Home › Code › extract_answers

extract_answers

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

extract_answers appears in the code Syntology harvested for 10 papers, as 10 distinct code bodies found in 10 places (a place is one code body under one paper). Of the 10 papers, 10 with a sample that ran: 7 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument. 3 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named extract_answers do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 10 distinct code bodies named extract_answers: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

1ran · honoured contract
0ran · violated contract
3ran · our draft was wrong
0ran; the contract check could not run
6ran
0unverified
3fingerprinted

Licence is a property of each copy, so it is counted per place: 3 of the 10 places are pointer only (Syntology does not serve that copy's text). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

10 papers shown of 10, newest first; 10 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive; 2 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

PaperDateFileStatus SyntologyLicence
Do Not Let Low-Probability Tokens Over-Dominate in RL for LLMs 19 May 2025 zhyang2226/ar-lopti/dataset_format.py 13606d906fd1dfa3 ran Apache-2.0 (permissive)
Extracting Affect Aggregates from Longitudinal Social Media Data with Temporal Adapters for Large Language Models 26 Sep 2024 dess-mannheim/temporal-adapters/extract_answers.py 50845729d38b2db5 ran MIT (permissive)
From Loops to Oops: Fallback Behaviors of Language Models Under Uncertainty 8 Jul 2024 Mivg/fallbacks/run_hallucinations_check.py 808e0a22c84796cd ran · our draft was wrong fingerprinted MIT (permissive)
An Investigation of Neuron Activation as a Unified Lens to Explain Chain-of-Thought Eliciting Arithmetic Reasoning of LLMs 18 Jun 2024 dakingrai/neuron-analysis-cot-arithmetic-reasoning/gsm8k_inference.py 86934d817edfb0b2 ran · honoured contract no licence file found · pointer only
Self-Explore: Enhancing Mathematical Reasoning in Language Models with Fine-grained Rewards 16 Apr 2024 hbin0701/Self-Explore/gen/utils_others.py fc107f0a7cb2bb77 ran · our draft was wrong no licence file found · pointer only
Bridging Pre-trained Models and Downstream Tasks for Source Code Understanding 4 Dec 2021 wangdeze18/DACL/algorithm_classification/evaluator/extract_answers.py bedbea7ed3a8588a ran MIT (permissive)
SD-QA: Spoken Dialectal Question Answering for the Real World 24 Sep 2021 ffaisal93/sd-qa/extract_qa_from_jsonl.py fd24ba8d7375d425 ran Apache-2.0 (permissive)
VQA: Visual Question Answering 3 May 2015 chirag26495/DAN_VQA/utils/build_vqa_inputs.py 0cf6e2086607dd93 ran · our draft was wrong no licence file found · pointer only
ACL Anthology id 2025.findings-acl.301 OpenBMB/ConsJudge/src/RAG_train/infer_acc.py 4fa8544d540bdcd7 ran fingerprinted MIT (permissive)
ACL Anthology id 2025.emnlp-main.796 yukyunglee/CheckEval/src/inference_checkeval.py dc1f5c8bd2851eb7 ran fingerprinted MIT (permissive)

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the harvest. "Pointer only" means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections