3 of 5 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; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 2 failures of our instrument; 2 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/2406.00922.json · badge: /api/ran/2406.00922.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 |
|---|---|---|
| stellalisy/mediq | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 1 no recorded run |
| stellali7/mediq | canonical (classifier label) classifier basis: census |
1 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| answer_to_idx | Ran ran, honoured the contract we drafted |
stellali7/mediq/src/expert_functions.py pointer only (licence: CC-BY-4.0); the stored copy get_code serves, from stellalisy/mediQ, is pointer only (licence: CC-BY-4.0) · get_code("d5dc134a218691e3") How it ranThe body of this sample is withheld: CC-BY-4.0, as GitHub detects it on this paper's repository, stellali7/mediq, 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. |
| load_data | Ran ran; our contract draft was wrong, not the code |
stellalisy/mediq/src/mediQ_benchmark.py pointer only (licence: CC-BY-4.0) · get_code("eab081cd0e4cf0fa") How it ranThe body of this sample is withheld: CC-BY-4.0, as GitHub detects it on this paper's repository, stellalisy/mediq, 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. |
| setup_logger | Ran ran; our contract draft was wrong, not the code |
stellalisy/mediq/src/mediQ_benchmark.py pointer only (licence: CC-BY-4.0) · get_code("4ca597d74af3490e") How it ranThe body of this sample is withheld: CC-BY-4.0, as GitHub detects it on this paper's repository, stellalisy/mediq, 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. |
| log_info | Not yet run unverified (harvested, no recorded run) |
stellali7/mediq/src/expert_basics.py pointer only (licence: CC-BY-4.0); the stored copy get_code serves, from stellalisy/mediQ, is pointer only (licence: CC-BY-4.0) · get_code("8bc8f393865d32f8") How it ranThe body of this sample is withheld: CC-BY-4.0, as GitHub detects it on this paper's repository, stellali7/mediq, 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. |
| run_patient_interaction | Not yet run unverified (harvested, no recorded run) |
stellalisy/mediq/src/mediQ_benchmark.py pointer only (licence: CC-BY-4.0) · get_code("78952645f76c9fd3") How it ranThe body of this sample is withheld: CC-BY-4.0, as GitHub detects it on this paper's repository, stellalisy/mediq, 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 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 5 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 5 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 |
|---|---|---|---|
| answer_to_idx | 1 other paper 1 later |
2603.05909 (2026-03) INFOGATHERER: Principled Information Seeking via Evidence Retrieval and Strategic Questioning |
|
| load_data | 1 other paper 1 later |
2603.05909 (2026-03) INFOGATHERER: Principled Information Seeking via Evidence Retrieval and Strategic Questioning |
|
| log_info | 1 other paper 1 later |
2603.05909 (2026-03) INFOGATHERER: Principled Information Seeking via Evidence Retrieval and Strategic Questioning |
|
| run_patient_interaction | 1 other paper 1 later |
2603.05909 (2026-03) INFOGATHERER: Principled Information Seeking via Evidence Retrieval and Strategic Questioning |
|
| setup_logger | 1 other paper 1 later |
2603.05909 (2026-03) INFOGATHERER: Principled Information Seeking via Evidence Retrieval and Strategic Questioning |
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.
Users typically engage with LLMs interactively, yet most existing benchmarks evaluate them in a static, single-turn format, posing reliability concerns in interactive scenarios. We identify a key obstacle towards reliability: LLMs are trained to answer any question, even with incomplete context or insufficient knowledge. In this paper, we propose to change the static paradigm to an interactive one, develop systems that proactively ask questions to gather more information and respond reliably, and introduce an benchmark - MediQ - to evaluate question-asking ability in LLMs. MediQ simulates clinical interactions consisting of a Patient System and an adaptive Expert System; with potentially incomplete initial information, the Expert refrains from making diagnostic decisions when unconfident, and instead elicits missing details via follow-up questions. We provide a pipeline to convert single-turn medical benchmarks into an interactive format. Our results show that directly prompting state-of-the-art LLMs to ask questions degrades performance, indicating that adapting LLMs to proactive information-seeking settings is nontrivial. We experiment with abstention strategies to better estimate model confidence and decide when to ask questions, improving diagnostic accuracy by 22.3%; however, performance still lags compared to an (unrealistic in practice) upper bound with complete information upfront. Further analyses show improved interactive performance with filtering irrelevant contexts and reformatting conversations. Overall, we introduce a novel problem towards LLM reliability, an interactive MediQ benchmark and a novel question-asking system, and highlight directions to extend LLMs' information-seeking abilities in critical domains.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2406.00922")
get_code_for_paper("2406.00922")
have("2406.00922")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2406.00922.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2406.00922)
Connect an agent — have() is free.