Qingyao Ai, Yiqun Liu, Zhijing Wu, Weihang Su, Yichen Tang
2 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; 2 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/2403.10081.json · badge: /api/ran/2403.10081.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 |
|---|---|---|
| oneal2000/dragin | canonical (classifier label) classifier basis not recorded on the link |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| bm25search_search | Ran ran; our contract draft was wrong, not the code |
oneal2000/dragin/src/retriever.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from thu-keg/seakr, is pointer only (licence: GPL-3.0) · get_code("1a724cf510e5bb93") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from thu-keg/seakr, and GPL-3.0, as GitHub detects it on that repository, is not in the permissive set Syntology serves inline. 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. |
| elasticsearch_lexical_multisearch | Ran ran; our contract draft was wrong, not the code |
oneal2000/dragin/src/retriever.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from thu-keg/seakr, is pointer only (licence: GPL-3.0) · get_code("0410394e1f61026a") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from thu-keg/seakr, and GPL-3.0, as GitHub detects it on that repository, is not in the permissive set Syntology serves inline. 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. |
| elasticsearch_hit_template | Not yet run unverified (harvested, no recorded run) |
oneal2000/dragin/src/retriever.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from thu-keg/seakr, is pointer only (licence: GPL-3.0) · get_code("189363ca95998f9a") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from thu-keg/seakr, and GPL-3.0, as GitHub detects it on that repository, is not in the permissive set Syntology serves inline. 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. No invocation 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 (1 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 |
|---|---|---|---|
| elasticsearch_hit_template | 3 other papers 1 dated earlier, 2 later |
2305.06983 (2023-05) Active Retrieval Augmented Generation |
2406.19215 (2024-06) SeaKR: Self-aware Knowledge Retrieval for Adaptive Retrieval Augmented Generation 2025.acl-long.548 (2025 (year only)) Improving Factuality with Explicit Working Memory |
| bm25search_search | 2 other papers 2 later |
2406.19215 (2024-06) SeaKR: Self-aware Knowledge Retrieval for Adaptive Retrieval Augmented Generation |
2025.acl-long.548 (2025 (year only)) Improving Factuality with Explicit Working Memory |
| elasticsearch_lexical_multisearch | 2 other papers 2 later |
2406.19215 (2024-06) SeaKR: Self-aware Knowledge Retrieval for Adaptive Retrieval Augmented Generation |
2025.acl-long.548 (2025 (year only)) Improving Factuality with Explicit Working Memory |
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.
Dynamic retrieval augmented generation (RAG) paradigm actively decides when and what to retrieve during the text generation process of Large Language Models (LLMs). There are two key elements of this paradigm: identifying the optimal moment to activate the retrieval module (deciding when to retrieve) and crafting the appropriate query once retrieval is triggered (determining what to retrieve). However, current dynamic RAG methods fall short in both aspects. Firstly, the strategies for deciding when to retrieve often rely on static rules. Moreover, the strategies for deciding what to retrieve typically limit themselves to the LLM's most recent sentence or the last few tokens, while the LLM's information needs may span across the entire context. To overcome these limitations, we introduce a new framework, DRAGIN, i.e., Dynamic Retrieval Augmented Generation based on the Information Needs of LLMs. Our framework is specifically designed to make decisions on when and what to retrieve based on the LLM's information needs during the text generation process. We evaluate DRAGIN along with existing methods comprehensively over 4 knowledge-intensive generation datasets. Experimental results show that DRAGIN achieves superior performance on all tasks, demonstrating the effectiveness of our method 1 .
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2403.10081")
get_code_for_paper("2403.10081")
have("2403.10081")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2403.10081.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2403.10081)
Connect an agent — have() is free.