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; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 3 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/2310.10322.json · badge: /api/ran/2310.10322.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 |
|---|---|---|
| mjy1111/bake | canonical (classifier label) classifier basis not recorded on the link |
3 ran · 2 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| binary_log_probs | Ran ran; our contract draft was wrong, not the code |
mjy1111/bake/easyeditor/trainer/losses.py pointer only (licence: NONE); the stored copy get_code serves, from MemEIC/MemEIC, is pointer only (licence: NONE) · get_code("27659a9c234ffb11") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, mjy1111/bake when it was checked. 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. |
| kl_loc_loss | Ran ran; our contract draft was wrong, not the code |
mjy1111/bake/easyeditor/trainer/losses.py pointer only (licence: NONE) · get_code("bcc592aa5c1e2bb3") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, mjy1111/bake when it was checked. 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. |
| masked_mean | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
mjy1111/bake/easyeditor/trainer/losses.py pointer only (licence: NONE) · get_code("e078eeed20f03838") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, mjy1111/bake when it was checked. 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. |
| get_model | Not yet run unverified (harvested, no recorded run) |
mjy1111/bake/easyeditor/trainer/models.py pointer only (licence: NONE); the stored copy get_code serves, from llm-editing/HalluEditBench, is pointer only (licence: NONE) · get_code("d2e4c1979dd70b9a") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, mjy1111/bake when it was checked. 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. |
| get_tokenizer | Not yet run unverified (harvested, no recorded run) |
mjy1111/bake/easyeditor/trainer/models.py pointer only (licence: NONE) · get_code("2defe42cf1a7f301") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, mjy1111/bake when it was checked. 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 (2 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 |
|---|---|---|---|
| binary_log_probs | 28 other papers 1 dated earlier, 27 later |
2210.07229 (2022-10) Mass-Editing Memory in a Transformer |
2311.09053 (2023-11) Assessing Knowledge Editing in Language Models via Relation Perspective 2024.acl-long.732 (2024 (year only)) MULFE: A Multi-Level Benchmark for Free Text Model Editing and 25 more not named here |
| kl_loc_loss | 16 other papers 16 later |
2401.04700 (2024-01) Model Editing Harms General Abilities of Large Language Models: Regularization to the Rescue |
2401.17623 (2024-01) Neighboring Perturbations of Knowledge Editing on Large Language Models 2402.11905 (2024-02) Learning to Edit: Aligning LLMs with Knowledge Editing and 13 more not named here |
| get_tokenizer | 14 other papers 14 later |
2401.04700 (2024-01) Model Editing Harms General Abilities of Large Language Models: Regularization to the Rescue |
2401.17623 (2024-01) Neighboring Perturbations of Knowledge Editing on Large Language Models 2402.11905 (2024-02) Learning to Edit: Aligning LLMs with Knowledge Editing and 11 more not named here |
| masked_mean | 10 other papers 1 dated earlier, 9 later |
2206.06520 (2022-06) Memory-Based Model Editing at Scale |
2406.11194 (2024-06) In-Context Editing: Learning Knowledge from Self-Induced Distributions 2407.06483 (2024-07) Composable Interventions for Language Models and 7 more not named here |
| get_model | 8 other papers 8 later |
2401.04700 (2024-01) Model Editing Harms General Abilities of Large Language Models: Regularization to the Rescue |
2402.11905 (2024-02) Learning to Edit: Aligning LLMs with Knowledge Editing 2404.15004 (2024-04) TAXI: Evaluating Categorical Knowledge Editing for Language Models and 5 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.
Large language models (LLMs) are prone to hallucinate unintended text due to false or outdated knowledge. Since retraining LLMs is resource intensive, there has been a growing interest in model editing. Despite the emergence of benchmarks and approaches, existing unidirectional editing and evaluation paradigms have failed to explore the reversal curse. In this paper, we study bidirectional language model editing, aiming to provide a rigorous evaluation to assess if edited LLMs can recall the editing knowledge bidirectionally. A metric of reverse generalization is introduced and a benchmark dubbed Bidirectional Assessment for Knowledge Editing (BAKE) is constructed to evaluate if post-edited models can recall the edited knowledge in the reverse direction of editing. We conduct extensive experiments using a variety of editing methods and LLMs. The results show that while most editing methods are able to accurately recall editing facts along the modification direction, they exhibit substantial systematic deficiencies when evaluating in the reverse direction. To further investigate the underlying causes of reversal curse and to explore potential strategies for mitigation, a detailed analysis is conducted from three perspectives. Our findings reveal that although In-Context Learning (ICL) can mitigate the reversal curse to a certain extent, it lacks continuity, is limited by the input length, and may introduce hallucinations. Therefore, combining the advantages of ICL and other editing methods is a promising direction for developing new editing paradigms.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2310.10322")
get_code_for_paper("2310.10322")
have("2310.10322")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2310.10322.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2310.10322)
Connect an agent — have() is free.