Home › Code › extract_label

extract_label

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_label appears in the code Syntology harvested for 12 papers, as 11 distinct code bodies found in 12 places (a place is one code body under one paper). Of the 12 papers, 11 with a sample that ran: 7 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument. 7 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_label 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 11 distinct code bodies named extract_label: 10 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 1 violated, 3 with no contract checked; 4 where Syntology's instrument failed) · 1 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:

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

Licence is a property of each copy, so it is counted per place: 9 of the 12 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

12 papers shown of 12, newest first; 12 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, and the graph's for 4 papers added by Syntology; 1 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
Adapting Reinforcement Learning with Chain-of-Thought Supervision for Explainable Detection of Hateful and Propagandistic Memes added by Syntology 2026-06 (from id) MohamedBayan/MemeReason/data_prep/build_unlabeled_training_set.py f85c65c949b629e1 ran · our draft was wrong fingerprinted no licence file found · pointer only
LAMUS: A Large-Scale Corpus for Legal Argument Mining from U.S. Caselaw using LLMs added by Syntology 2026-03 (from id) LavanyaPobbathi/LAMUS/code/experiment/A_run_4_models_1st.py 33a56252e8d12114 ran · our draft was wrong fingerprinted no licence file found · pointer only
DRIV-EX: Counterfactual Explanations for Driving LLMs added by Syntology 2026-03 (from id) Amaia-CARDIEL/DRIV_EX/driv_ex/dataset/generate_input_only_highD_data.py 48ce3f13567e8ce8 ran · honoured contract BSD-3-Clause (permissive)
Ask a Strong LLM Judge when Your Reward Model is Uncertain added by Syntology 2025-10 (from id) zhenghaoxu-gatech/uncertainty-router/ppo/src/eval_pm_router/eval_rewardbench.py 1acad12079a57e2a ran · honoured contract fingerprinted no licence file found · pointer only
SubjECTive-QA: Measuring Subjectivity in Earnings Call Transcripts' QA Through Six-Dimensional Feature Analysis 28 Oct 2024 gtfintechlab/SubjECTive-QA/scripts/openai_benchmarking.py 828a7266ccb957bb ran · our draft was wrong fingerprinted licence not identified · pointer only
LLaMA-Berry: Pairwise Optimization for O1-like Olympiad-Level Mathematical Reasoning 3 Oct 2024 trotsky1997/mathblackbox/gen_mcts_dpo.py f4e59a05a34d24d9 ran · our draft was wrong fingerprinted no licence file found · pointer only
From Theft to Bomb-Making: The Ripple Effect of Unlearning in Defending Against Jailbreak Attacks 3 Jul 2024 thu-coai/safeunlearning/evaluation/score_shieldlm.py 470eb9f49a78b466 ran no licence file found · pointer only
Resolving Discrepancies in Compute-Optimal Scaling of Language Models 27 Jun 2024 formll/resolving-scaling-law-discrepencies/paper_tables.py 9370894d3db38de0 unverified MIT (permissive)
CritiqueLLM: Towards an Informative Critique Generation Model for Evaluation of Large Language Model Generation 30 Nov 2023 thu-coai/critiquellm/evaluation/eval_pairwise.py 0164dbe04ac52b71 ran · violated contract fingerprinted no licence file found · pointer only
Sentiment Analysis in the Era of Large Language Models: A Reality Check 24 May 2023 damo-nlp-sg/llm-sentiment/evaluate.py 10ef73cfeb03a631 ran fingerprinted MIT recorded; this copy not marked cleared · pointer only
Hephaestus: A large scale multitask dataset towards InSAR understanding 20 Apr 2022 orion-ai-lab/hephaestus/utilities/annotation_utils.py d64c1408c1ae7f8d ran MIT (permissive)
ACL Anthology id 2024.findings-naacl.246 DAMO-NLP-SG/LLM-Sentiment/evaluate.py 10ef73cfeb03a631 ran fingerprinted MIT recorded; this copy not marked cleared · pointer only

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