Mitesh Khapra, Sahana Ramnath, Preksha Nema, Deep Sahni
3 of 3 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; 3 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/2010.08983.json · badge: /api/ran/2010.08983.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 |
|---|---|---|
| iitmnlp/BERT-Analysis-RCQA | canonical (classifier label) classifier basis: classifier_2025 |
1 ran · 0 no recorded run |
| copy not recorded | community not in the paper's declared repositories |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_tokens | Ran ran; our contract draft was wrong, not the code |
this paper's copy was not recorded; identical code first harvested from saptarshi059/cdqa-project pointer only; the stored copy get_code serves, from saptarshi059/cdqa-project, is pointer only (licence: NONE) · get_code("aa6bc32d9c17a2f1") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. 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. |
| make_qid_to_has_ans | Ran ran; our contract draft was wrong, not the code |
iitmnlp/BERT-Analysis-RCQA/bert/evaluate-v2.0.py code served (permissive licence) · get_code("e91c44f5680827e2") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned dict. 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.
|
| normalize_answer | Ran ran; our contract draft was wrong, not the code |
this paper's copy was not recorded; identical code first harvested from saptarshi059/cdqa-project pointer only; the stored copy get_code serves, from saptarshi059/cdqa-project, is pointer only (licence: NONE) · get_code("6a96435eba311b08") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. 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 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 3 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 |
|---|---|---|---|
| normalize_answer | 37 other papers 11 dated earlier, 26 later · 1 only as an assembly brick |
1808.07042 (2018-08) CoQA: A Conversational Question Answering Challenge |
1810.04805 (2018-10) BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding 1902.01718 (2019-02) End-to-End Open-Domain Question Answering with BERTserini and 34 more not named here |
| get_tokens | 25 other papers 7 dated earlier, 18 later |
1810.04805 (2018-10) BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding |
1902.01718 (2019-02) End-to-End Open-Domain Question Answering with BERTserini 1908.08962 (2019-08) Well-Read Students Learn Better: On the Importance of Pre-training Compact Models and 22 more not named here |
| make_qid_to_has_ans | 9 other papers 5 dated earlier, 4 later |
1810.04805 (2018-10) BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding |
1908.08962 (2019-08) Well-Read Students Learn Better: On the Importance of Pre-training Compact Models 1910.01244 (2019-10) Linking artificial and human neural representations of language and 6 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.
BERT and its variants have achieved stateof-the-art performance in various NLP tasks. Since then, various works have been proposed to analyze the linguistic information being captured in BERT. However, the current works do not provide an insight into how BERT is able to achieve near human-level performance on the task of Reading Comprehension based Question Answering. In this work, we attempt to interpret BERT for RCQA. Since BERT layers do not have predefined roles, we define a layer's role or functionality using Integrated Gradients. Based on the defined roles, we perform a preliminary analysis across all layers. We observed that the initial layers focus on query-passage interaction, whereas later layers focus more on contextual understanding and enhancing the answer prediction. Specifically for quantifier questions (how much/how many), we notice that BERT focuses on confusing words (i.e., on other numerical quantities in the passage) in the later layers, but still manages to predict the answer correctly. The fine-tuning and analysis scripts will be publicly available at https://github.com/ iitmnlp/BERT-Analysis-RCQA.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2010.08983")
get_code_for_paper("2010.08983")
have("2010.08983")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2010.08983.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2010.08983)
Connect an agent — have() is free.