6 of 7 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, 1 violated it and 5 have no contract verdict; 0 failures of our instrument; 1 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/2104.00640.json · badge: /api/ran/2104.00640.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 |
|---|---|---|
| knot-fit-but/claimdissector | community (classifier label) classifier basis not recorded on the link |
6 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| exact_match_score | Ran ran, violated the contract we drafted |
knot-fit-but/claimdissector/src/common/eval_utils.py code served (permissive licence) · get_code("efa3643614e9c5f5") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned bool, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| f1_score | Ran ran on a synthesized input |
knot-fit-but/claimdissector/src/common/eval_utils.py code served (permissive licence) · get_code("6b3ccf76356a23b7") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned float, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| find_sub_list | Ran ran on a synthesized input |
knot-fit-but/claimdissector/src/common/utility.py code served (permissive licence) · get_code("c26a0a5333ae5ba2") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 2, dtype family int; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| normalize_answer | Ran ran on a synthesized input |
knot-fit-but/claimdissector/src/common/eval_utils.py code served (permissive licence) · get_code("8ddaf8aae0f76d1e") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| share_list | Ran ran on a synthesized input |
knot-fit-but/claimdissector/src/common/distributed_utils.py code served (permissive licence) · get_code("dad0b1b31bc66fa9") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 2, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| unicode_normalize | Ran ran on a synthesized input |
knot-fit-but/claimdissector/src/common/utility.py code served (permissive licence) · get_code("ccff200d6bb6d6fd") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| arg_topk | Not yet run unverified (harvested, no recorded run) |
knot-fit-but/claimdissector/src/common/utility.py code served (permissive licence) · get_code("90cb252a65c0643e") How it ranno invocation recorded. |
Of 7 samples lifted from this paper's linked repositories, 7 carry a function identity and 0 do not. Of the 7 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 1 later) and 5 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 |
|---|---|---|---|
| exact_match_score | 56 other papers 26 dated earlier, 29 later, 1 same year, order not determinable |
1508.06615 (2015-08) Character-Aware Neural Language Models |
1606.05250 (2016-06) SQuAD: 100,000+ Questions for Machine Comprehension of Text 1608.07905 (2016-08) Machine Comprehension Using Match-LSTM and Answer Pointer and 53 more not named here |
| find_sub_list | 1 other paper 1 dated earlier |
2008.12804 (2020-08) Rethinking the Objectives of Extractive Question Answering |
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 fact-checking systems verify claims against evidence to predict their veracity. In real-world scenarios, the retrieved evidence may not unambiguously support or refute the claim and yield conflicting but valid interpretations. Existing fact-checking datasets assume that the models developed with them predict a single veracity label for each claim, thus discouraging the handling of such ambiguity. To address this issue we present AmbiFC, a fact-checking dataset with 10k claims derived from real-world information needs. It contains fine-grained evidence annotations of 50k passages from 5k Wikipedia pages. We analyze the disagreements arising from ambiguity when comparing claims against evidence in AmbiFC, observing a strong correlation of annotator disagreement with linguistic phenomena such as underspecification and probabilistic reasoning. We develop models for predicting veracity handling this ambiguity via soft labels and find that a pipeline that learns the label distribution for sentence-level evidence selection and veracity prediction yields the best performance. We compare models trained on different subsets of AmbiFC and show that models trained on the ambiguous instances perform better when faced with the identified linguistic phenomena.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2104.00640")
get_code_for_paper("2104.00640")
have("2104.00640")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2104.00640.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2104.00640)
Connect an agent — have() is free.