Sunkyung Lee, Minjin Choi, Jongwuk Lee
5 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, 0 violated it and 0 have no contract verdict; 5 failures of our instrument; 2 no recorded run), measured 2026-11-22; 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/2311.03057.json · badge: /api/ran/2311.03057.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 |
|---|---|---|
| skleee/GLEN | canonical (classifier label) classifier basis: census |
3 ran · 2 no recorded run |
| castorini/docTTTTTquery | canonical (classifier label) classifier basis: census |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| augment | Ran ran; our contract draft was wrong, not the code |
skleee/GLEN/src/tevatron/datasets/glen_p1_dataset.py code served (permissive licence) · get_code("10b3d1379c9c469a") 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.
|
| augment | Ran ran; our contract draft was wrong, not the code |
skleee/GLEN/src/tevatron/datasets/glen_p2_dataset.py code served (permissive licence) · get_code("ebb2ee7e575e7730") 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.
|
| load_data | Ran ran; our contract draft was wrong, not the code |
skleee/GLEN/src/tevatron/datasets/glen_p1_dataset.py code served (permissive licence) · get_code("e286f7d0aefcda6b") 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 tuple. 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.
|
| process_text | Ran ran; our contract draft was wrong, not the code |
castorini/docTTTTTquery/convert_msmarco_passage_to_anserini.py code served (permissive licence) · get_code("4631c7e2bb826903") 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 1, 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.
|
| split_new_repeated | Ran ran; our contract draft was wrong, not the code |
castorini/docTTTTTquery/convert_msmarco_passage_to_anserini.py code served (permissive licence) · get_code("db69e1633f087c8f") 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 tuple, 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.
|
| load_data | Not yet run unverified (harvested, no recorded run) |
skleee/GLEN/src/tevatron/datasets/glen_p2_dataset.py code served (permissive licence) · get_code("75422425ae81213e") How it ranno invocation recorded. |
| load_tf_weights_in_t5 | Not yet run unverified (harvested, no recorded run) |
skleee/GLEN/src/tevatron/modeling/glen_t5_modeling.py code served (permissive licence) · get_code("33fcca2adb353b5f") 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, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 7 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.
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.
Generative retrieval shed light on a new paradigm of document retrieval, aiming to directly generate the identifier of a relevant document for a query. While it takes advantage of bypassing the construction of auxiliary index structures, existing studies face two significant challenges: (i) the discrepancy between the knowledge of pre-trained language models and identifiers and (ii) the gap between training and inference that poses difficulty in learning to rank. To overcome these challenges, we propose a novel generative retrieval method, namely Generative retrieval via LExical iNdex learning (GLEN). For training, GLEN effectively exploits a dynamic lexical identifier using a two-phase index learning strategy, enabling it to learn meaningful lexical identifiers and relevance signals between queries and documents. For inference, GLEN utilizes collisionfree inference, using identifier weights to rank documents without additional overhead. Experimental results prove that GLEN achieves stateof-the-art or competitive performance against existing generative retrieval methods on various benchmark datasets, e.g., NQ320k, MS MARCO, and BEIR. The code is available at https://github.com/skleee/GLEN.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2311.03057")
get_code_for_paper("2311.03057")
have("2311.03057")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2311.03057.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2311.03057)
Connect an agent — have() is free.