2 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/1706.09799.json · badge: /api/ran/1706.09799.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| Maluuba/nlg-eval | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| dec | Ran ran; our contract draft was wrong, not the code |
Maluuba/nlg-eval/nlgeval/pycocoevalcap/meteor/meteor.py pointer only (licence: NOASSERTION) · get_code("ba9348aac71a3f72") How it ranThe body of this sample is withheld: GitHub could not classify the licence of this paper's repository, Maluuba/nlg-eval (NOASSERTION). The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| enc | Ran ran; our contract draft was wrong, not the code |
Maluuba/nlg-eval/nlgeval/pycocoevalcap/meteor/meteor.py pointer only (licence: NOASSERTION) · get_code("eaab50b5d9fea58a") How it ranThe body of this sample is withheld: GitHub could not classify the licence of this paper's repository, Maluuba/nlg-eval (NOASSERTION). The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 2 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 2 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| dec | 4 other papers 4 later |
2109.08365 (2021-09) CodeQA: A Question Answering Dataset for Source Code Comprehension |
2022.findings-naacl.160 (2022 (year only)) Learning Structural Information for Syntax-Controlled Paraphrase Generation 2309.09812 (2023-09) R2GenGPT: Radiology Report Generation with Frozen LLMs and 1 more not named here |
| enc | 4 other papers 4 later |
2109.08365 (2021-09) CodeQA: A Question Answering Dataset for Source Code Comprehension |
2022.findings-naacl.160 (2022 (year only)) Learning Structural Information for Syntax-Controlled Paraphrase Generation 2309.09812 (2023-09) R2GenGPT: Radiology Report Generation with Frozen LLMs and 1 more not named here |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Automated metrics such as BLEU are widely used in the machine translation literature. They have also been used recently in the dialogue community for evaluating dialogue response generation. However, previous work in dialogue response generation has shown that these metrics do not correlate strongly with human judgment in the non task-oriented dialogue setting. Task-oriented dialogue responses are expressed on narrower domains and exhibit lower diversity. It is thus reasonable to think that these automated metrics would correlate well with human judgment in the task-oriented setting where the generation task consists of translating dialogue acts into a sentence. We conduct an empirical study to confirm whether this is the case. Our findings indicate that these automated metrics have stronger correlation with human judgments in the task-oriented setting compared to what has been observed in the non task-oriented setting. We also observe that these metrics correlate even better for datasets which provide multiple ground truth reference sentences. In addition, we show that some of the currently available corpora for task-oriented language generation can be solved with simple models and advocate for more challenging datasets.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("1706.09799")
get_code_for_paper("1706.09799")
have("1706.09799")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/1706.09799.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/1706.09799)
Connect an agent — have() is free.