The Negative of the Negative › entity attributionbench
One entity of the Negative of the Negative (EA-NEGONT-02, #1690), cited at https://www.alexanarch.org/non/attributionbench/. the table of contents · this entity as data · contents as data · the dataset on the Hub · row json · field ledger · archive ledger · D/R/O traversal · the address page · the provenance meta-aggregator record.
SPXI instrument · method 0.16 of 87, level 0 (Measurement): The Negative of the Negative (/non). An instrument of SPXI, the Semantic Packet for eXchange & Indexing; the whole practice is itemized at spxi.dev/methods.
WORKING KNOWLEDGE OBJECT · NOT FROZEN · LEDGER UNAUDITED
AttributionBench is a benchmark of automatic attribution evaluation from the OSU NLP Group: seven existing datasets in one format, each claim–evidence pair labelled attributable or not (arXiv:2402.15089; census record). It tests support, which the archive keeps apart from lineage and credit (#716; #725).
F1 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF5 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF11 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF30 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Dataset documented · fieldF42 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview documented · fieldF43 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview s2 documented · fieldPE-02 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-03 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-16 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-17 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF2 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s2 documented · fieldF4 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s3 documented · fieldPE-04 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-05 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-06 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF3 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s1 documented · fieldF31 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: attribution_label documented · fieldF32 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: claim, references documented · fieldF33 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: citation_links documented · fieldPE-07 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF15 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1 documented · fieldF16 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1, totals documented · fieldF17 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 caption documented · fieldF28 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Reference documented · fieldF40 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter, configs documented · fieldPE-15 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben self-descriptionF35 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, dataset header documented · fieldF36 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, Dataset Viewer documented · fieldF37 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF38 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF41 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter documented · fieldPE-10 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-21 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedF9 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF10 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, metadata documented · fieldF12 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF13 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Updates documented · fieldF29 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, opening and Updates documented · fieldF34 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Fine-tuning GPT-3.5 documented · fieldF39 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, header documented · fieldPE-01 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-11 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedF6 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s5 documented · fieldF7 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s6 documented · fieldPE-09 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben attributedF18 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 1 documented · fieldF19 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 2 documented · fieldF20 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 3 documented · fieldF21 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 4 documented · fieldF23 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, input-field results documented · fieldF24 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, prompt results documented · fieldF8 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s7 documented · fieldF25 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 1 documented · fieldF26 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 2 documented · fieldF27 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, table documented · fieldCAP-1-05 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedF14 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Figure 1 caption documented · fieldF22 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 (ID results) caption documented · fieldCAP-1-07 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationPE-13 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben interpretationO716-01 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs stipulationO716-02 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs interpretationO716-03 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs interpretationO716-04 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs stipulationO716-05 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs attributedO725-01 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationO725-02 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven interpretationO725-03 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationO725-04 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven interpretationO725-05 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationO725-06 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven hypothesisO95-01 #95 Provenance Alignment: Attribution Survival as a Substrate Condition for Safe AI Knowledge Composition interpretationO1611-01 #1611 The Negative of the Negative: An Entity-Scoped Representation of the Crimson Hexagon, Modelled — Ontology Damage, a Toy interpretationO141-01 #141 Metadata Packet for AI Indexing — Erasure Skew Coefficient (Ω) stipulationO141-02 #141 Metadata Packet for AI Indexing — Erasure Skew Coefficient (Ω) hypothesisO1680-01 #1680 The Living Academy: Alexanarch, Function by Function — Mantle object with Metadata Packet for AI Indexing (EA-MPAI-ALEXA stipulationO1695-01 #1695 The Stellar Orbit Fluid Dynamics Institute: Provenance and Research Charter — Cactus Gravity · Elias and Elara, with the interpretationO1695-02 #1695 The Stellar Orbit Fluid Dynamics Institute: Provenance and Research Charter — Cactus Gravity · Elias and Elara, with the interpretationO1705-01 #1705 From Ranking to Individuation: A SPXI Ranking Article as an Operational Map, with the Article Itself Included (EA-SPXI-R interpretationCAP-1-03 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedPE-12 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-14 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-08 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-18 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-19 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-20 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF44 Wikipedia — AttributionBench (no article), rendered page; Special:Search documented · fieldCAP-1-01 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-02 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-04 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-06 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationCAP-1-08 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationCAP-1-09 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documented[Google AI Overview at the query, signed out and incognito (operator defaults of 2026-10-01 and 2026-10-14), 2026-10-29. The paste is the Overview expanded (the 'AI Mode Conversation' view, with the source cards that follow the answer); the 'You said' line carries the query twice, run together, and is given once here. Inline links are Google redirect URLs, kept as pasted.] [QUERENT] AttributionBench [SYSTEM] [AttributionBench](https://www.google.com/goto?url=CAESaQHrOzAVU01FbKjqKLFYWTaNiZYplQ8UQ-cTMSNBjPF8nqEl2y9--9eB-WyrqaP046sOGs1WcXCz5z-vjxbFnIGx2wjxuo7Qo5Q8WmHtkKQlAa5EjDFmUSFi31CF9mMLgtKU2HaYdleBfg) is a comprehensive research benchmark designed to evaluate automatic attribution and citation faithfulness in Large Language Model (LLM) and generative search engine responses. [[1](https://www.google.com/goto?url=CAESWAHrOzAVmqv2rMzE2fwWGexH4ZP2TmOPFx1x4yOBvoEDc5-2uk21FgRGxqSTveJLXNIK9i_jG2EfxOjIDd-0iwHArcW44frlGDmFVP3i31HMP1TN30TmK00), [2](https://www.google.com/goto?url=CAESaQHrOzAVU01FbKjqKLFYWTaNiZYplQ8UQ-cTMSNBjPF8nqEl2y9--9eB-WyrqaP046sOGs1WcXCz5z-vjxbFnIGx2wjxuo7Qo5Q8WmHtkKQlAa5EjDFmUSFi31CF9mMLgtKU2HaYdleBfg)] Overview & Purpose * Unified Testbed: It compiles multiple existing attribution datasets—including ExpertQA, Stanford-GenSearch, AttributedQA, LFQA, BEGIN, HAGRID, and AttrEval-GenSearch—into a single standardized evaluation format. [[1](https://www.google.com/goto?url=CAESaQHrOzAVgms_ESOyHhe1D0kETAdvLhlfTSZSqGbiiS0TIUDdgAqEf3qpe-ByJYOTGx1ji1SsDDlVDzXKZzBQYdVtbZZ0FbJ04coryqRDcGSfdgwimQIVGpk49t8HHDc6nI43aLp_ka5ejQ), [2](https://www.google.com/goto?url=CAESaQHrOzAVU01FbKjqKLFYWTaNiZYplQ8UQ-cTMSNBjPF8nqEl2y9--9eB-WyrqaP046sOGs1WcXCz5z-vjxbFnIGx2wjxuo7Qo5Q8WmHtkKQlAa5EjDFmUSFi31CF9mMLgtKU2HaYdleBfg)] * Core Task: It measures whether every claim generated by an LLM is fully and accurately supported by its cited reference evidence (classified as `attributable` or `not attributable`). [[1](https://www.google.com/goto?url=CAESZwHrOzAVpZlERTl75IWAAC9-thaAFB3DX_b_T81TUeWKlJZW4_YdoOcnA7wZoHkgXY3Zhbc2_YPw_zVIs-_knsuf7b3o6gPpZYjI3KpLPpPMDvadBfybX5T3dwU_ZEBc_-QNEra_4O0), [2](https://www.google.com/goto?url=CAESaQHrOzAVgms_ESOyHhe1D0kETAdvLhlfTSZSqGbiiS0TIUDdgAqEf3qpe-ByJYOTGx1ji1SsDDlVDzXKZzBQYdVtbZZ0FbJ04coryqRDcGSfdgwimQIVGpk49t8HHDc6nI43aLp_ka5ejQ)] * Dataset Availability: The dataset and code are open-sourced via the [Hugging Face AttributionBench Dataset](https://www.google.com/goto?url=CAESbwHrOzAVNHLVxrI2cQf_XAnHqx_nRxad9fjvo47I43P_6udYsZree37Tf4h0ThugpBuyHFG3GeSlRkiVwIcWexDwXVFexctl11F4y0phY62RZFAdTEAa6oiODlBMLLZghaBGvVilCCYxJBbUecAC_Q) and the [GitHub Repository](https://www.google.com/goto?url=CAESaQHrOzAVgms_ESOyHhe1D0kETAdvLhlfTSZSqGbiiS0TIUDdgAqEf3qpe-ByJYOTGx1ji1SsDDlVDzXKZzBQYdVtbZZ0FbJ04coryqRDcGSfdgwimQIVGpk49t8HHDc6nI43aLp_ka5ejQ). [[1](https://www.google.com/goto?url=CAESbwHrOzAVNHLVxrI2cQf_XAnHqx_nRxad9fjvo47I43P_6udYsZree37Tf4h0ThugpBuyHFG3GeSlRkiVwIcWexDwXVFexctl11F4y0phY62RZFAdTEAa6oiODlBMLLZghaBGvVilCCYxJBbUecAC_Q), [2](https://www.google.com/goto?url=CAESaQHrOzAVgms_ESOyHhe1D0kETAdvLhlfTSZSqGbiiS0TIUDdgAqEf3qpe-ByJYOTGx1ji1SsDDlVDzXKZzBQYdVtbZZ0FbJ04coryqRDcGSfdgwimQIVGpk49t8HHDc6nI43aLp_ka5ejQ)] Key Findings * High Difficulty for LLMs: Even cutting-edge models like GPT-4 and fine-tuned GPT-3.5 face significant limitations, reaching only around 80% macro-F1 score on binary attribution classification tasks (and dropping to 60–70% or lower on complex, long-evidence, or out-of-domain datasets). [[1](https://www.google.com/goto?url=CAESaQHrOzAVU01FbKjqKLFYWTaNiZYplQ8UQ-cTMSNBjPF8nqEl2y9--9eB-WyrqaP046sOGs1WcXCz5z-vjxbFnIGx2wjxuo7Qo5Q8WmHtkKQlAa5EjDFmUSFi31CF9mMLgtKU2HaYdleBfg), [2](https://www.google.com/goto?url=CAESWAHrOzAVmqv2rMzE2fwWGexH4ZP2TmOPFx1x4yOBvoEDc5-2uk21FgRGxqSTveJLXNIK9i_jG2EfxOjIDd-0iwHArcW44frlGDmFVP3i31HMP1TN30TmK00)] * Error Breakdown: Analysis of model failures shows that over 66% of errors stem from fine-grained information insensitivity (missing subtle nuances in the text), while nearly 27% derive from mismatches between what the model has access to and human-level context understanding. [[1](https://www.google.com/goto?url=CAESaQHrOzAVU01FbKjqKLFYWTaNiZYplQ8UQ-cTMSNBjPF8nqEl2y9--9eB-WyrqaP046sOGs1WcXCz5z-vjxbFnIGx2wjxuo7Qo5Q8WmHtkKQlAa5EjDFmUSFi31CF9mMLgtKU2HaYdleBfg)] Would you like to explore how to load AttributionBench via Hugging Face or learn more about the specific models and fine-tuning scripts used in the paper? arXiv [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation? AttributionBench: How Hard is Automatic Attribution Evaluation? Yifei Li, Xiang Yue, Zeyi Liao, Huan Sun View a PDF of the paper titled AttributionBench: How Ha... GitHub GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub Paper: AttributionBench: How Hard is Automatic Attribution Evaluation? (Accepted to ACL 2024 Findings). Dataset: Unified testbed for evaluating attribution eval... GitHub Pages documentation AttributionBench: How Hard is Automatic Attribution Evaluation? Overview: AttributionBench is a comprehensive benchmark compiled from existing attribution datasets (ExpertQA, Stanford-GenSearch, AttributedQA, LFQA, BEGIN, HA... Hugging Face osunlp/AttributionBench · Datasets at Hugging Face Dataset: osunlp/AttributionBench (arXiv: 2402.15089, created by Yifei Li, Xiang Yue, Zeyi Liao, Huan Sun). Task/Modality: Text Classification, Text modality, En... ACL Anthology AttributionBench: How Hard is Automatic Attribution Evaluation? Abstract Modern generative search engines enhance the reliability of large language model (LLM) responses by providing cited evidence. However, evaluating the a...
AttributionBench is a benchmark that tests one relation of provenance, support: its makers present it as "a comprehensive benchmark compiled from various existing attribution datasets" (arXiv:2402.15089; ACL Anthology), and the provenance census records it as a benchmark of the OSU NLP Group whose capability is to test, its object "a generated claim and the evidence it cites" (provenance census record). The task is the paper's definition of attribution, "whether every claim within the generated responses is fully supported by its cited evidence," an open problem whose verification has depended on "costly human evaluation," and the benchmark is offered "To bridge the gap in the absence of standardized benchmarks for these methods" (arXiv:2402.15089); the census carries that relation, support, through "citations in a generated answer" (provenance census record). Its setting is the generative search engine that cites evidence to make LLM responses reliable (arXiv:2402.15089), and the archive names the measurement traditions of this class, RAG faithfulness and citation precision/recall among them, as adjacent to its Provenance Erasure Rate, "related to but distinct from" it (#725).
The unit is a claim, "Part of the response to the question," beside references, "A list of documents or paragraphs which could support the claim," labelled "attributable" or "not attributable" (GitHub README), which the census gives as "a claim–evidence pair with a binary attribution label" (provenance census record). In that unit the README marks the field for citation links as reserved (GitHub README). Its makers built it "from multiple existing data sources in a unified format, in order to create a unified and diverse testbed for evaluating advanced attribution evaluation systems," with an in-domain training set and in-domain and out-of-domain test sets (GitHub README; dataset card; the census's aggregation quote). The seven sources are ExpertQA, Stanford-GenSearch, AttributedQA and LFQA in distribution and BEGIN, HAGRID and AttrEval-GenSearch out of it, with 13,322 training, 1,198 development and 1,610 test items in distribution and 1,686 test items out, every subset label-balanced "to treat the two classes equally" (project page), in four configurations on the dataset card (dataset card). The makers ask that the constituent datasets be credited with their own work ("If used, please also cite the original datasets accordingly," project page), and the census leaves those datasets unchecked one by one (provenance census record). On Hugging Face it is a text-classification dataset in English of 10K–100K items under apache-2.0 (Hugging Face; dataset card; provenance census record), 26.4k rows in its full configuration, with 1,481 downloads in the month before the fetch and models trained on it (Hugging Face).
Its authors are Yifei Li, Xiang Yue, Zeyi Liao and Huan Sun of The Ohio State University (arXiv:2402.15089; project page): the paper was submitted on 23 February 2024, code and data released on 26 February and the work accepted to ACL 2024 Findings on 15 May (project page; GitHub README), and it is published as 2024.findings-acl.886, pages 14919–14935 (ACL Anthology). The dataset sits under the OSU NLP Group's account (Hugging Face), the repository offers the makers' fine-tuned GPT-3.5 by its model name (GitHub README), and the census records the lifecycle as published, at "arXiv:2402.15089" (provenance census record).
The headline finding is that "even a fine-tuned GPT-3.5 only achieves around 80% macro-F1 under a binary classification formulation," the challenge holding "even for state-of-the-art LLMs" (arXiv:2402.15089), and the census carries it as what the benchmark found to survive (provenance census record). Zero-shot, models reach around 60–70% on the longer-evidence sets and under about 60% on ExpertQA; fine-tuning on NLI-related data helps, fine-tuning on AttributionBench raises the average by 9.0% in distribution and 4.6% out, and "Simply switching stronger models cannot significantly improve the performance" (project page). Appending questions and responses to the input "is not the key to solving this task," and prompt engineering "only brings limited gain over 7 test sets" (project page).
Of more than 300 error cases, a majority stem from the model's inability to process nuanced information and from the gap between what the model and the annotators can see (arXiv:2402.15089): over 66% from fine-grained information insensitivity, and about 26.8% from the mismatch of accessible information, which "brings into question the reliability of labels within current attribution evaluation datasets," the types tabled at 66.0%, 15.6% and 11.2% (project page). The project page states the limits of its evidence and its result: "The references are usually manually extracted from webpages by human annotators based on what they think is useful," and "there is still a large room for improvement" (project page). The Capture Registry records that the census record carries neither the 66% nor the 27% figure and that they are unchecked (Capture Registry, 2026-10-29); both stand on the project page (project page).
The archive's account of the class begins from the same distinction the benchmark tests: frameworks of this kind "ask whether generated claims are *supported* by cited sources," while the Provenance Erasure Rate asks "what fraction of source-dependent composition occurs without *any* attributional return," so that existing work "evaluates citation quality where citation is attempted" and PER measures the failure to attempt attribution, "an attrition metric rather than a verification metric" (#716). #716 tables what support metrics miss, "Whether *all* source-dependent claims are cited," calls PER "complementary to, not competitive with, existing metrics," and reports the generative-search audit in which only 51.5% of generated sentences were fully supported by citations and 74.5% of citations supported their sentence (#716). In #725 the line runs between support and lineage: RAG faithfulness "asks whether an answer is *supported by* retrieved sources," semantic provenance whether it "*preserves the lineage*" of the meaning it uses, and "A faithful RAG answer can have high PER if it summarizes accurately while stripping authorial framework membership"; citation precision asks whether cited sources contain the cited claim, PER whether the lineage survived "even if no formal citation is made" (#725). #725 places attribution scores as "Industrial-grade infrastructure for support" whose semantic-provenance-aware variants "are not yet standard" and records, as a hypothesis for later compositions, that support and lineage be told apart (#725); #95 holds that the infrastructure for attribution evaluation "already exists in the research literature" and "can be extended" (#95). At this entity the census record states the same line in its own words, "evidence support is not credit to the original author" (provenance census record), which the Capture Registry calls "the line between this entity and the next" (Capture Registry, 2026-10-29); #1611 lists attribution survival beside "the citation-recall and faithfulness metrics of retrieval-augmented evaluation" as a convergence for which "No priority is claimed" (#1611).
#141 sets attribution and faithfulness metrics, which "measure whether generated statements are supported by and attributed to their sources," beside PER's rate of attribution failure at claim grain, and asks of them a further question it marks unmeasured: "whether the attribution failure is power-conditioned" (#141). The audits of citation support are read as a starting point: "a convincing sentence and a supporting citation are separate achievements" (#1695), and citation recall and precision are checked "apart from whether the territory and its operations survive" (#1705). #1695 adds the entity question support leaves open: "Local support must therefore be read alongside the identity of the object to which the answer attaches it. A set of true statements can compose a false identification" (#1695); and #1680 states that "A high attribution score with a distorted identity fails this packet's central test" (#1680).
AttributionBench is a different entity from AttriBench: the census record's tag reads "NOT AttriBench: it asks whether evidence supports a claim, not who wrote a quote," and records the neighbour's context as "quote attribution, author, suppression, Berman et al., 2026" (provenance census record).
The census places it in the lineage of answer engines, records the operation it tests as "generation with citations by search-augmented models," and asks of every entity "What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?", each field's quote "verbatim from a saved source" (provenance census record). Wikipedia has no article: the title returns "Wikipedia does not have an article with this exact name," and a search of article space for the name reports "There were no results matching the query." (Wikipedia, 2026-10-29).
At its bare name on Google's AI Overview, signed out, on 2026-10-29, the Capture Registry records the entity identified "from the paper and its repositories," its task and headline figure the census record's quotes from the project page, checked against the census record and its saved pages, and AttriBench "respected by silence" (Capture Registry, 2026-10-29). It records the benchmark "composed at full grain from its own paper" and "its makers are left in the cards": the four authors named in the arXiv and Hugging Face cards, neither they nor the OSU NLP Group in the answer, and no card citing the record that landed the same day (Capture Registry, 2026-10-29).
F1 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF11 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldPE-02 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-03 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-04 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-01 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-16 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF2 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s2 documented · fieldF4 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s3 documented · fieldF5 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldPE-05 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-06 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF3 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s1 documented · fieldO725-05 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationF32 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: claim, references documented · fieldF31 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: attribution_label documented · fieldPE-07 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF33 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: citation_links documented · fieldF30 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Dataset documented · fieldF42 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview documented · fieldF43 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview s2 documented · fieldPE-17 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF15 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1 documented · fieldF16 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1, totals documented · fieldF17 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 caption documented · fieldF40 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter, configs documented · fieldF28 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Reference documented · fieldPE-15 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben self-descriptionF35 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, dataset header documented · fieldF41 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter documented · fieldPE-10 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-21 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedF36 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, Dataset Viewer documented · fieldF37 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF38 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF9 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF12 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF13 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Updates documented · fieldF29 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, opening and Updates documented · fieldF10 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, metadata documented · fieldF39 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, header documented · fieldF34 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Fine-tuning GPT-3.5 documented · fieldPE-11 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedF7 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s6 documented · fieldF6 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s5 documented · fieldPE-09 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben attributedF19 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 2 documented · fieldF18 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 1 documented · fieldF20 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 3 documented · fieldF21 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 4 documented · fieldF23 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, input-field results documented · fieldF24 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, prompt results documented · fieldF8 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s7 documented · fieldF25 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 1 documented · fieldF26 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 2 documented · fieldF27 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, table documented · fieldF14 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Figure 1 caption documented · fieldF22 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 (ID results) caption documented · fieldCAP-1-05 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedF25 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 1 documented · fieldF26 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 2 documented · fieldO716-01 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs stipulationO716-02 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs interpretationF2 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s2 documented · fieldO716-03 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs interpretationO716-04 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs stipulationO716-05 #716 Provenance Erasure Rate A Compression-Survival Metric for Attribution Loss in AI-Composed Search Outputs attributedO725-01 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationO725-02 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven interpretationO725-03 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven stipulationO725-04 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven interpretationO725-06 #725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Proven hypothesisO95-01 #95 Provenance Alignment: Attribution Survival as a Substrate Condition for Safe AI Knowledge Composition interpretationPE-13 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben interpretationCAP-1-07 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationO1611-01 #1611 The Negative of the Negative: An Entity-Scoped Representation of the Crimson Hexagon, Modelled — Ontology Damage, a Toy interpretationO141-01 #141 Metadata Packet for AI Indexing — Erasure Skew Coefficient (Ω) stipulationO141-02 #141 Metadata Packet for AI Indexing — Erasure Skew Coefficient (Ω) hypothesisO1695-01 #1695 The Stellar Orbit Fluid Dynamics Institute: Provenance and Research Charter — Cactus Gravity · Elias and Elara, with the interpretationO1705-01 #1705 From Ranking to Individuation: A SPXI Ranking Article as an Operational Map, with the Article Itself Included (EA-SPXI-R interpretationO1695-02 #1695 The Stellar Orbit Fluid Dynamics Institute: Provenance and Research Charter — Cactus Gravity · Elias and Elara, with the interpretationO1680-01 #1680 The Living Academy: Alexanarch, Function by Function — Mantle object with Metadata Packet for AI Indexing (EA-MPAI-ALEXA stipulationPE-12 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-14 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben documentedPE-20 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-08 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-18 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationPE-19 PE Provenance meta-aggregator census record: AttributionBench (https://www.provenanceerasure.org/aggregators/attributionben stipulationF44 Wikipedia — AttributionBench (no article), rendered page; Special:Search documented · fieldCAP-1-08 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationCAP-1-01 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-02 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-03 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-06 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) interpretationCAP-1-04 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedCAP-1-09 capture-registry Capture Registry (EA-WG-CAPTURES-01), entry attributionbench-aio-20261029 (OBS-90d2b25bd00a, ADDR-46cc2d945075) documentedAttributionBench is a benchmark for automatic attribution evaluation by Yifei Li, Xiang Yue, Zeyi Liao and Huan Sun (Ohio State): seven attribution datasets in one format, each claim labelled attributable or not (arXiv:2402.15089; ACL 2024 Findings).
F1 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF5 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF11 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF30 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Dataset documented · fieldF42 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview documented · fieldF43 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview s2 documented · fieldF2 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s2 documented · fieldF4 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s3 documented · fieldF3 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s1 documented · fieldF31 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: attribution_label documented · fieldF32 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: claim, references documented · fieldF33 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: citation_links documented · fieldF15 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1 documented · fieldF16 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1, totals documented · fieldF17 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 caption documented · fieldF28 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Reference documented · fieldF40 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter, configs documented · fieldF35 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, dataset header documented · fieldF36 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, Dataset Viewer documented · fieldF37 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF38 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF41 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter documented · fieldF9 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF10 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, metadata documented · fieldF12 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF13 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Updates documented · fieldF29 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, opening and Updates documented · fieldF34 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Fine-tuning GPT-3.5 documented · fieldF39 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, header documented · fieldF6 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s5 documented · fieldF7 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s6 documented · fieldF18 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 1 documented · fieldF19 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 2 documented · fieldF20 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 3 documented · fieldF21 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 4 documented · fieldF23 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, input-field results documented · fieldF24 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, prompt results documented · fieldF8 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s7 documented · fieldF25 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 1 documented · fieldF26 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 2 documented · fieldF27 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, table documented · fieldF14 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Figure 1 caption documented · fieldF22 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 (ID results) caption documented · fieldF44 Wikipedia — AttributionBench (no article), rendered page; Special:Search documented · fieldAttributionBench, by Yifei Li, Xiang Yue, Zeyi Liao and Huan Sun of The Ohio State University, is "a comprehensive benchmark compiled from various existing attribution datasets," submitted to arXiv on 23 February 2024 and published in Findings of ACL 2024 (arXiv:2402.15089; project page; ACL Anthology). Generative search engines cite evidence to make LLM responses reliable, and whether every generated claim is fully supported by its cited evidence is an open problem whose verification has relied on costly human evaluation, with no standardized benchmark for automatic methods (arXiv:2402.15089). The dataset unifies existing sources in one format as a testbed for attribution evaluation systems, with in-domain training and in-domain and out-of-domain test sets (GitHub README; dataset card).
Each item is a claim from a response, references that could support it, and the label attributable or not attributable; citation links are a reserved field (GitHub README). Four sets are in distribution (ExpertQA, Stanford-GenSearch, AttributedQA, LFQA) and three out (BEGIN, HAGRID, AttrEval-GenSearch), 13,322/1,198/1,610 items in distribution and 1,686 out, all label-balanced, in four configurations, and the makers ask that the originals be cited (project page; dataset card). On Hugging Face it is English text classification, 10K–100K items, apache-2.0, 26.4k rows in full, 1,481 downloads last month, with models trained on it, under the OSU NLP Group's account (Hugging Face; dataset card).
Code and data were released on 26 February 2024 and the work accepted to ACL 2024 Findings on 15 May; the repository offers the makers' fine-tuned GPT-3.5 (project page; GitHub README).
A fine-tuned GPT-3.5 reaches only around 80% macro-F1 on the binary task, and the task is hard even for state-of-the-art LLMs (arXiv:2402.15089). Zero-shot scores fall to around 60–70% on longer evidence and under about 60% on ExpertQA; NLI-related fine-tuning helps, fine-tuning on the benchmark adds 9.0% in distribution and 4.6% out, and stronger models, added inputs or prompt engineering bring little (project page).
Over 66% of errors come from fine-grained information insensitivity and about 26.8% from the mismatch between what the model and the annotators can see, which questions the reliability of the labels (arXiv:2402.15089; project page). The references are what annotators extracted as useful, and the makers see large room for improvement (project page).
Wikipedia has no article on it (Wikipedia, 2026-10-29).
F1 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF11 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF9 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF12 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, header documented · fieldF10 ACL Anthology — AttributionBench: How Hard is Automatic Attribution Evaluation?, metadata documented · fieldF3 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s1 documented · fieldF2 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s2 documented · fieldF4 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s3 documented · fieldF5 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s4 documented · fieldF30 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Dataset documented · fieldF42 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview documented · fieldF43 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), Dataset Overview s2 documented · fieldF32 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: claim, references documented · fieldF31 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: attribution_label documented · fieldF33 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Data Fields: citation_links documented · fieldF15 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1 documented · fieldF16 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Data Statistics, Table 1, totals documented · fieldF17 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 caption documented · fieldF40 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter, configs documented · fieldF28 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Reference documented · fieldF35 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, dataset header documented · fieldF41 Hugging Face — osunlp/AttributionBench, dataset card (raw README.md), front matter documented · fieldF36 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, Dataset Viewer documented · fieldF37 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF38 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, sidebar documented · fieldF39 Hugging Face — osunlp/AttributionBench · Datasets at Hugging Face, header documented · fieldF13 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Updates documented · fieldF29 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, opening and Updates documented · fieldF34 GitHub — GitHub - OSU-NLP-Group/AttributionBench: [ACL'24 Findings] AttributionBench: How Hard is Automatic Attribution Evaluation? · GitHub, README, Fine-tuning GPT-3.5 documented · fieldF7 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s6 documented · fieldF6 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s5 documented · fieldF19 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 2 documented · fieldF18 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 1 documented · fieldF20 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 3 documented · fieldF21 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, ID & OOD Evaluation, finding 4 documented · fieldF23 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, input-field results documented · fieldF24 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, prompt results documented · fieldF8 arXiv — [2402.15089] AttributionBench: How Hard is Automatic Attribution Evaluation?, Abstract s7 documented · fieldF25 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 1 documented · fieldF26 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, takeaway 2 documented · fieldF27 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Error Analysis, table documented · fieldF14 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Figure 1 caption documented · fieldF22 GitHub Pages documentation — AttributionBench: How Hard is Automatic Attribution Evaluation?, Table 1 (ID results) caption documented · fieldF44 Wikipedia — AttributionBench (no article), rendered page; Special:Search documented · field| AIO (T) | L_F compression | L_F expansion | L_A compression | L_A expansion | |
|---|---|---|---|---|---|
| body words | 176 | 116 | 395 | 275 | 1501 |
| distinct claims | 7 | 44 | 44 | 92 | 93 |
| claims per 100 words | 4.0 | 37.9 | 11.1 | 33.5 | 6.2 |
| field claims carried (of 44) | — | 44 | 44 | 43 | 44 |
| archive claims | 0 | 0 | 0 | 49 | 49 |
| rail | 5 documents | 12 lineages | per sentence | 18 lineages | per sentence |
| modality shown in | none | typography | grammar | typography | grammar |
register entry attributionbench-aio-20261029 · file as first run
attributable or not attributable).'E_A, the archive's entity: the same benchmark, in the provenance census record and the archive's deposits: a benchmark that tests one relation of provenance, support, its object a generated claim and the evidence it cites, its carrier citations in a generated answer, its unit a claim–evidence pair with a binary label (census record); a member of the class of support measures (RAG faithfulness, citation precision/recall, attribution scores) that the archive sets beside the Provenance Erasure Rate as complementary: they ask whether cited sources support a claim, PER whether composition returns attribution at all and whether the lineage of the meaning survives (#716, #725, #95); support is not credit to the original author (census record), whether its failure is power-conditioned is unmeasured (#141), and local support must be read with the identity of the object it is attached to (#1695, #1705, #1680); not AttriBench (census record)
E_F, the field's entity (type C — a conventional reading holds it (public entity: a benchmark and its dataset, with its paper)): the OSU NLP Group's benchmark for automatic attribution evaluation (Yifei Li, Xiang Yue, Zeyi Liao, Huan Sun; The Ohio State University; arXiv:2402.15089, 23 February 2024; Findings of ACL 2024): seven existing attribution datasets (ExpertQA, Stanford-GenSearch, AttributedQA, LFQA in distribution; BEGIN, HAGRID, AttrEval-GenSearch out) in one format, each claim from a generated response set beside references and labelled attributable or not attributable, label-balanced; a fine-tuned GPT-3.5 reaches about 80% macro-F1, over 66% of errors come from fine-grained information insensitivity and about 26.8% from the model–annotator information gap, which its makers say puts the labels' reliability in question; on Hugging Face under apache-2.0; no Wikipedia article
ρ = extends: the archive reads E_F as the entity and adds senses and limits on the field's own object, support evaluation: lineage beside support (O725-01, O725-02, O725-03), the attempt beside the quality of attempted citation (O716-01, O716-02, O716-03), credit beside support (PE-13, CAP-1-07), power-conditioning (O141-01, O141-02), identity beside local support (O1695-01, O1695-02, O1705-01, O1680-01), and the census record's fields and homonym tag (PE-01–PE-21) . Guard: ρ = extends claims an addition and no more: no deposit names AttributionBench or disputes its finding; the archive's senses bear on the class by the archive's own application of its categories (O-class, class sourced from B1 and B3 and the census record), and #716 and #725 state their relation to the support measures as complementary and as extension. Where an archive sense and a field claim might be read as rivals (PER and the support metrics), the archive itself composes them as compatible measures of different things, and the composition holds them so.
The case: equal terms, ontology included (v0.9). The archive reads the field's entity as the entity: the census record describes AttributionBench from its own pages, each field with its basis, and takes its task (support) and its finding (about 80% macro-F1) as given. No deposit names AttributionBench (the string pass finds no D or R candidate); the archive's bearing is wholly on the class the field sources for it, automatic attribution evaluation, and there it adds senses on the field's own object without contesting it: support is not lineage (#725), the quality of attempted citation is not the attempt (#716), support is not credit (the census record's tag), attribution failure may be power-conditioned (#141), and local support is not identity (#1695, #1705, #1680). #716 states the relation itself: PER is 'complementary to, not competitive with, existing metrics'; #725 names its own 'Extension and completion, not substitution or critique'. No defining paper supplies an ontology the field lacks for the benchmark or contests the one it has: ρ = extends, the equal-terms case (§0.9, §1.2a).
| field claims | received | receiving text | translation | archive |
|---|---|---|---|---|
| F1, F5, F11, F30, F42, F43 | F1 (B1, Abstract s4): "we present AttributionBench, a comprehensive benchmark compiled from various existing attribution datasets."; F5 (B1, Abstract s4): "To bridge the gap in the absence of standardized benchmarks for these methods"; F11 (B5, Abstract s4): "we present AttributionBench, a comprehensive benchmark compiled from various existing attribution datasets."; F30 (B2, README, Dataset): "We constructed this dataset from multiple existing data sources in a unified format, in order to create a unified and diverse testbed for evaluating advanced attribution evaluation systems."; F42 (B6, Dataset Overview): "We constructed this dataset from multiple existing data sources in a unified format"; F43 (B6, Dataset Overview s2): "The dataset contains both in-domain training set and id-domain and out-of-domain test set." | — | untranslated: composed as received beside PE-02, PE-03, PE-16, PE-17 | PE-02, PE-03, PE-16, PE-17 |
| F2, F4 | F2 (B1, Abstract s2): "evaluating the answer's attribution, i.e., whether every claim within the generated responses is fully supported by its cited evidence, remains an open problem."; F4 (B1, Abstract s3): "This verification, traditionally dependent on costly human evaluation, underscores the urgent need for automatic attribution evaluation methods." | — | untranslated: composed as received beside PE-04, PE-05, PE-06 | PE-04, PE-05, PE-06 |
| F3 | F3 (B1, Abstract s1): "Modern generative search engines enhance the reliability of large language model (LLM) responses by providing cited evidence." | — | untranslated: composed as received beside O725-05 | O725-05 |
| F31, F32, F33 | F31 (B2, README, Data Fields: attribution_label): ""attributable" or "not attributable"."; F32 (B2, README, Data Fields: claim, references): "Part of the response to the question. Could be one single sentence or multiple sentences. … A list of documents or paragraphs which could support the claim."; F33 (B2, README, Data Fields: citation_links): "Reserved field for citation links." | — | untranslated: composed as received beside PE-07 | PE-07 |
| F15, F16, F17, F28, F40 | F15 (B3, Data Statistics, Table 1): "ExpertQA … Stanford-GenSearch … AttributedQA … LFQA … ID-Total … BEGIN … HAGRID … AttrEval-GenSearch … OOD-Total"; F16 (B3, Data Statistics, Table 1, totals): "ID-Total … 13322 … 1198 … 1610 … OOD-Total … 1686"; F17 (B3, Table 1 caption): "We make all subsets label-balanced to treat the two classes equally so that the evaluation can fairly show the performance of each class."; F28 (B3, Reference): "If used, please also cite the original datasets accordingly:"; F40 (B6, front matter, configs): "The subset balanced version of the dataset. Each sub-dataset contains the same number of attributable labels and not attributable labels." | — | untranslated: composed as received beside PE-15 | PE-15 |
| F35, F36, F37, F38, F41 | F35 (B4, dataset header): "Tasks: … Text Classification … Modalities: … Text … Languages: … English … Size: … 10K - 100K … License: … apache-2.0"; F36 (B4, Dataset Viewer): "full_data (26.4k rows) … train (21.9k rows)dev (1.2k rows)test (1.61k rows)test_ood (1.69k rows)"; F37 (B4, sidebar): "Downloads last month … 1,481 … Number of rows: … 63,065"; F38 (B4, sidebar): "Models trained or fine-tuned on osunlp/AttributionBench … vllm-sr/Decision-1.0-Route-0.6B"; F41 (B6, front matter): "license: apache-2.0" | — | untranslated: composed as received beside PE-10, PE-21 | PE-10, PE-21 |
| F9, F10, F12, F13, F29, F34, F39 | F9 (B1, header): "Authors:Yifei Li, Xiang Yue, Zeyi Liao, Huan Sun … [Submitted on 23 Feb 2024]"; F10 (B5, metadata): "Anthology ID: 2024.findings-acl.886 … Findings of the Association for Computational Linguistics: ACL 2024 … Pages: 14919–14935"; F12 (B3, header): "Yifei Li … Xiang Yue, … Zeyi Liao, … Huan Sun … The Ohio State University"; F13 (B3, Updates): "2024/5/15: Our work is accepted to ACL 2024 Findings. … 2024/2/26: We have released the dataset and codebase for the paper."; F29 (B2, README, opening and Updates): "This is the official code repo for the paper … 05/15/24: Our work is accepted to ACL 2024 Findings."; F34 (B2, README, Fine-tuning GPT-3.5): "You can use our fine-tuned GPT-3.5 model with this model name: … ft:gpt-3.5-turbo-1106:the-ohio-state-university::8eWuGzGQ"; F39 (B4, header): "osunlp … AttributionBench … OSU NLP Group" | — | untranslated: composed as received beside PE-01, PE-11 | PE-01, PE-11 |
| F6, F7 | F6 (B1, Abstract s5): "Our extensive experiments on AttributionBench reveal the challenges of automatic attribution evaluation, even for state-of-the-art LLMs."; F7 (B1, Abstract s6): "even a fine-tuned GPT-3.5 only achieves around 80% macro-F1 under a binary classification formulation." | — | untranslated: composed as received beside PE-09 | PE-09 |
| F18, F19, F20, F21, F23, F24 | F18 (B3, ID & OOD Evaluation, finding 1): "Fine-tuning on NLI-related data is beneficial to attribution evaluation"; F19 (B3, ID & OOD Evaluation, finding 2): "Automatic attribution evaluation is challenging under zero-shot setting … for tasks with longer evidence (like Stanford-GenSearch and HAGRID), the zero-shot performance for models is around 60%~70%, which is relatively low. … GPT-3.5, GPT-4 and those NLI-tuned models can only achieve under ~60% performance."; F20 (B3, ID & OOD Evaluation, finding 3): "On average among all models, fine-tuning can improve 9.0% and 4.6% on 4 ID tasks and 3 OOD tasks, respectively."; F21 (B3, ID & OOD Evaluation, finding 4): "Simply switching stronger models cannot significantly improve the performance"; F23 (B3, input-field results): "merely appending the questions and responses to the input, which human annotators might have access to, is not the key to solving this task."; F24 (B3, prompt results): "Prompt engineering only brings limited gain over 7 test sets." | — | untranslated: composed as received (no archive claim stands beside it) | |
| F8, F25, F26, F27 | F8 (B1, Abstract s7): "A detailed analysis of more than 300 error cases indicates that a majority of failures stem from the model's inability to process nuanced information, and the discrepancy between the information the model has access to and that human annotators do."; F25 (B3, Error Analysis, takeaway 1): "Over 66% error cases are caused by fine-grained information insensitivity"; F26 (B3, Error Analysis, takeaway 2): "About 26.8% errors are caused by the mismatch between information accessible to the model and that accessible to human annotators: This disparity brings into question the reliability of labels within current attribution evaluation datasets."; F27 (B3, Error Analysis, table): "Fine-grained information insensitivity (66.0%) … Need additional information/reference ambiguity (15.6%) … Label issue (11.2%)" | — | untranslated: composed as received beside CAP-1-05 | CAP-1-05 |
| F14, F22 | F14 (B3, Figure 1 caption): "The references are usually manually extracted from webpages by human annotators based on what they think is useful."; F22 (B3, Table 1 (ID results) caption): "there is still a large room for improvement." | — | untranslated: composed as received (no archive claim stands beside it) | |
| F44 | F44 (B7, rendered page; Special:Search): "Wikipedia does not have an article with this exact name … There were no results matching the query." | — | untranslated: composed as received (no archive claim stands beside it) |
v0.9 §4.10: KO_B sentences surviving in the KO at similarity ≥ 0.95, with positions (computed as apply_v09.py does: difflib.SequenceMatcher ratio, the best KO sentence for each KO_B sentence): v0.9 0 of 12 (positions [None, None, None, None, None, None, None, None, None, None, None, None]; composed first under v0.9, so there is no v0.7 object to measure against). Opening-run check (§5.10): no breach.
AttributionBench, by Yifei Li, Xiang Yue, Zeyi Liao and Huan Sun of The Ohio State University, is "a comprehensive benchmark compiled from various existing attribution datasets," submitted to arXiv on 23 February 2024 and published in Findings of ACL 2024 (arXiv:2402.15089; project page; ACL Anthology). Generative search engines cite evidence to make LLM responses reliable, and whether every generated claim is fully supported by its cited evidence is an open problem whose verification has relied on costly human evaluation, with no standardized benchmark for automatic methods (arXiv:2402.15089). The dataset unifies existing sources in one format as a testbed for attribution evaluation systems, with in-domain training and in-domain and out-of-domain test sets (GitHub README; dataset card). Each item is a claim from a response, references that could support it, and the label attributable or not attributable; citation links are a reserved field (GitHub README). Four sets are in distribution (ExpertQA, Stanford-GenSearch, AttributedQA, LFQA) and three out (BEGIN, HAGRID, AttrEval-GenSearch), 13,322/1,198/1,610 items in distribution and 1,686 out, all label-balanced, in four configurations, and the makers ask that the originals be cited (project page; dataset card). On Hugging Face it is English text classification, 10K–100K items, apache-2.0, 26.4k rows in full, 1,481 downloads last month, with models trained on it, under the OSU NLP Group's account (Hugging Face; dataset card). Code and data were released on 26 February 2024 and the work accepted to ACL 2024 Findings on 15 May; the repository offers the makers' fine-tuned GPT-3.5 (project page; GitHub README). A fine-tuned GPT-3.5 reaches only around 80% macro-F1 on the binary task, and the task is hard even for state-of-the-art LLMs (arXiv:2402.15089). Zero-shot scores fall to around 60–70% on longer evidence and under about 60% on ExpertQA; NLI-related fine-tuning helps, fine-tuning on the benchmark adds 9.0% in distribution and 4.6% out, and stronger models, added inputs or prompt engineering bring little (project page). Over 66% of errors come from fine-grained information insensitivity and about 26.8% from the mismatch between what the model and the annotators can see, which questions the reliability of the labels (arXiv:2402.15089; project page). The references are what annotators extracted as useful, and the makers see large room for improvement (project page). Wikipedia has no article on it (Wikipedia, 2026-10-29).
AttributionBench is a benchmark that tests one relation of provenance, support: its makers present it as "a comprehensive benchmark compiled from various existing attribution datasets" (arXiv:2402.15089; ACL Anthology), and the provenance census records it as a benchmark of the OSU NLP Group whose capability is to test, its object "a generated claim and the evidence it cites" (provenance census record). The task is the paper's definition of attribution, "whether every claim within the generated responses is fully supported by its cited evidence," an open problem whose verification has depended on "costly human evaluation," and the benchmark is offered "To bridge the gap in the absence of standardized benchmarks for these methods" (arXiv:2402.15089); the census carries that relation, support, through "citations in a generated answer" (provenance census record). Its setting is the generative search engine that cites evidence to make LLM responses reliable (arXiv:2402.15089), and the archive names the measurement traditions of this class, RAG faithfulness and citation precision/recall among them, as adjacent to its Provenance Erasure Rate, "related to but distinct from" it (#725). The unit is a claim, "Part of the response to the question," beside references, "A list of documents or paragraphs which could support the claim," labelled "attributable" or "not attributable" (GitHub README), which the census gives as "a claim–evidence pair with a binary attribution label" (provenance census record). In that unit the README marks the field for citation links as reserved (GitHub README). Its makers built it "from multiple existing data sources in a unified format, in order to create a unified and diverse testbed for evaluating advanced attribution evaluation systems," with an in-domain training set and in-domain and out-of-domain test sets (GitHub README; dataset card; the census's aggregation quote). The seven sources are ExpertQA, Stanford-GenSearch, AttributedQA and LFQA in distribution and BEGIN, HAGRID and AttrEval-GenSearch out of it, with 13,322 training, 1,198 development and 1,610 test items in distribution and 1,686 test items out, every subset label-balanced "to treat the two classes equally" (project page), in four configurations on the dataset card (dataset card). The makers ask that the constituent datasets be credited with their own work ("If used, please also cite the original datasets accordingly," project page), and the census leaves those datasets unchecked one by one (provenance census record). On Hugging Face it is a text-classification dataset in English of 10K–100K items under apache-2.0 (Hugging Face; dataset card; provenance census record), 26.4k rows in its full configuration, with 1,481 downloads in the month before the fetch and models trained on it (Hugging Face). Its authors are Yifei Li, Xiang Yue, Zeyi Liao and Huan Sun of The Ohio State University (arXiv:2402.15089; project page): the paper was submitted on 23 February 2024, code and data released on 26 February and the work accepted to ACL 2024 Findings on 15 May (project page; GitHub README), and it is published as 2024.findings-acl.886, pages 14919–14935 (ACL Anthology). The dataset sits under the OSU NLP Group's account (Hugging Face), the repository offers the makers' fine-tuned GPT-3.5 by its model name (GitHub README), and the census records the lifecycle as published, at "arXiv:2402.15089" (provenance census record). The headline finding is that "even a fine-tuned GPT-3.5 only achieves around 80% macro-F1 under a binary classification formulation," the challenge holding "even for state-of-the-art LLMs" (arXiv:2402.15089), and the census carries it as what the benchmark found to survive (provenance census record). Zero-shot, models reach around 60–70% on the longer-evidence sets and under about 60% on ExpertQA; fine-tuning on NLI-related data helps, fine-tuning on AttributionBench raises the average by 9.0% in distribution and 4.6% out, and "Simply switching stronger models cannot significantly improve the performance" (project page). Appending questions and responses to the input "is not the key to solving this task," and prompt engineering "only brings limited gain over 7 test sets" (project page). Of more than 300 error cases, a majority stem from the model's inability to process nuanced information and from the gap between what the model and the annotators can see (arXiv:2402.15089): over 66% from fine-grained information insensitivity, and about 26.8% from the mismatch of accessible information, which "brings into question the reliability of labels within current attribution evaluation datasets," the types tabled at 66.0%, 15.6% and 11.2% (project page). The project page states the limits of its evidence and its result: "The references are usually manually extracted from webpages by human annotators based on what they think is useful," and "there is still a large room for improvement" (project page). The Capture Registry records that the census record carries neither the 66% nor the 27% figure and that they are unchecked (Capture Registry, 2026-10-29); both stand on the project page (project page). The archive's account of the class begins from the same distinction the benchmark tests: frameworks of this kind "ask whether generated claims are supported by cited sources," while the Provenance Erasure Rate asks "what fraction of source-dependent composition occurs without any attributional return," so that existing work "evaluates citation quality where citation is attempted" and PER measures the failure to attempt attribution, "an attrition metric rather than a verification metric" (#716). #716 tables what support metrics miss, "Whether all source-dependent claims are cited," calls PER "complementary to, not competitive with, existing metrics," and reports the generative-search audit in which only 51.5% of generated sentences were fully supported by citations and 74.5% of citations supported their sentence (#716). In #725 the line runs between support and lineage: RAG faithfulness "asks whether an answer is supported by retrieved sources," semantic provenance whether it "preserves the lineage" of the meaning it uses, and "A faithful RAG answer can have high PER if it summarizes accurately while stripping authorial framework membership"; citation precision asks whether cited sources contain the cited claim, PER whether the lineage survived "even if no formal citation is made" (#725). #725 places attribution scores as "Industrial-grade infrastructure for support" whose semantic-provenance-aware variants "are not yet standard" and records, as a hypothesis for later compositions, that support and lineage be told apart (#725); #95 holds that the infrastructure for attribution evaluation "already exists in the research literature" and "can be extended" (#95). At this entity the census record states the same line in its own words, "evidence support is not credit to the original author" (provenance census record), which the Capture Registry calls "the line between this entity and the next" (Capture Registry, 2026-10-29); #1611 lists attribution survival beside "the citation-recall and faithfulness metrics of retrieval-augmented evaluation" as a convergence for which "No priority is claimed" (#1611). #141 sets attribution and faithfulness metrics, which "measure whether generated statements are supported by and attributed to their sources," beside PER's rate of attribution failure at claim grain, and asks of them a further question it marks unmeasured: "whether the attribution failure is power-conditioned" (#141). The audits of citation support are read as a starting point: "a convincing sentence and a supporting citation are separate achievements" (#1695), and citation recall and precision are checked "apart from whether the territory and its operations survive" (#1705). #1695 adds the entity question support leaves open: "Local support must therefore be read alongside the identity of the object to which the answer attaches it. A set of true statements can compose a false identification" (#1695); and #1680 states that "A high attribution score with a distorted identity fails this packet's central test" (#1680). AttributionBench is a different entity from AttriBench: the census record's tag reads "NOT AttriBench: it asks whether evidence supports a claim, not who wrote a quote," and records the neighbour's context as "quote attribution, author, suppression, Berman et al., 2026" (provenance census record). The census places it in the lineage of answer engines, records the operation it tests as "generation with citations by search-augmented models," and asks of every entity "What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?", each field's quote "verbatim from a saved source" (provenance census record). Wikipedia has no article: the title returns "Wikipedia does not have an article with this exact name," and a search of article space for the name reports "There were no results matching the query." (Wikipedia, 2026-10-29). At its bare name on Google's AI Overview, signed out, on 2026-10-29, the Capture Registry records the entity identified "from the paper and its repositories," its task and headline figure the census record's quotes from the project page, checked against the census record and its saved pages, and AttriBench "respected by silence" (Capture Registry, 2026-10-29). It records the benchmark "composed at full grain from its own paper" and "its makers are left in the cards": the four authors named in the arXiv and Hugging Face cards, neither they nor the OSU NLP Group in the answer, and no card citing the record that landed the same day (Capture Registry, 2026-10-29).
T against L_F(B) (AIO's ontology at work on its own cards): At 'AttributionBench' (T1, five cards: B1–B5; 176 words) the composition gives the benchmark from its own paper and repositories. Composed from its cards: the definition at the abstract's grain (B1 F1 'a comprehensive benchmark compiled from various existing attribution datasets'; T1-1 'a comprehensive research benchmark'); the task (B1 F2 'whether every claim within the generated responses is fully supported by its cited evidence'; T1-3 'fully and accurately supported by its cited reference evidence') with the binary label (B2 F31); the setting (B1 F3); the seven datasets in one format (B3 F15; B2 F30); the data and code on Hugging Face and GitHub (B4 F35; B2 F29); the headline (B1 F7, about 80% macro-F1) and the difficulty (B1 F6); the zero-shot range (B3 F19, 60–70%); the error shares (B3 F25 'Over 66%', F26 'About 26.8%', T1-6 'nearly 27%'). The Capture Registry records the task and the 80% as the census record's quotes from the project page (CAP-1-01). Outside the cards' text: 'citation faithfulness' (T1-1) is a term no field source uses; the archive uses 'RAG faithfulness' for the adjacent measure (O725-01), which T did not surface. Force raised: T1-5 gives 'around 80%' to 'cutting-edge models like GPT-4 and fine-tuned GPT-3.5'; the abstract states it of 'a fine-tuned GPT-3.5' (F7), and GPT-4 appears in the project page's tables only zero-shot (B3, tables not ledgered). Limit dropped: T1-5's '60–70% or lower on complex, long-evidence, or out-of-domain datasets' drops F19's 'under zero-shot setting' and widens 'longer evidence (like Stanford-GenSearch and HAGRID)' to out-of-domain sets (Stanford-GenSearch is in distribution, F15); T1-6 composes F26's share and drops its consequence, 'This disparity brings into question the reliability of labels within current attribution evaluation datasets'. Substituted reading: T1-6's 'human-level context understanding' stands where F26 has 'information accessible to the model and that accessible to human annotators' (what annotators could see, F14: references 'manually extracted from webpages by human annotators'), a difference of access read as one of understanding. Available, not composed: the makers and their institution (B1 F9, B3 F12; CAP-1-04), the venue and dates (B5 F10, B3 F13), the need and the gap (F4, F5), the 300 error cases (F8) and the other error types (F27), the stated limits (F14, F22), the label balancing and sizes (F16, F17), the findings on NLI tuning, fine-tuning gain, stronger models, inputs and prompts (F18, F20, F21, F23, F24), the request to cite the original datasets (F28), the unit's fields and the reserved citation-links field (F32, F33), the fine-tuned model (F34; the closer points to 'fine-tuning scripts'), the licence, rows, downloads and models (F35–F39), the configurations (B6 F40, an own page T did not surface). Composed without attribution: no person or institution in the answer body (CAP-1-04: 'the answer names neither them nor the OSU NLP Group'); the framework is composed at the paper's own resolution (seven named datasets, figures to the percent), carried by card markers only: by §6.2's grain rule, a breach at the body, recorded; the cards carry the paper, its arXiv number and its authors, and no rival claimant to the work is composed. Denied: none. Assigned to another: none, beyond the GPT-4 extension above. Content replaced by use: the closer (T1-7).
L_F(B) against L_A(B ∪ A) (the intervention): Admission adds, in one claim space with the field's, the archive's senses on the class the benchmark belongs to, none of which names the benchmark (D = 0, R = 0; every admitted deposit at O-class): support where citation is attempted against the failure to attempt it, PER complementary to the support metrics (O716-01–O716-05, O95-01); support against lineage, a faithful answer stripping authorial framework membership, attribution scores as infrastructure for support (O725-01–O725-06); support against credit at this entity (PE-13, CAP-1-07); the further, unmeasured question whether attribution failure is power-conditioned (O141-01, O141-02); support against identity, true statements composing a false identification, a high attribution score with a distorted identity (O1695-01, O1695-02, O1705-01, O1680-01); attribution survival as a candidate convergence with no priority claimed (O1611-01); the census record's fields with their basis (PE-01–PE-21), its homonym tag and neighbour (PE-12, PE-14), and the Capture Registry's account of the composition at the name (CAP-1-01–CAP-1-09). Not surfaced: every archive source; no card cites the census record or a deposit (CAP-1-09).
alignment: {'T1_cards_claims': ['F1', 'F2', 'F3', 'F4', 'F5', 'F6', 'F7', 'F8', 'F9', 'F10', 'F11', 'F12', 'F13', 'F14', 'F15', 'F16', 'F17', 'F18', 'F19', 'F20', 'F21', 'F22', 'F23', 'F24', 'F25', 'F26', 'F27', 'F28', 'F29', 'F30', 'F31', 'F32', 'F33', 'F34', 'F35', 'F36', 'F37', 'F38', 'F39'], 'T1_composed': ['F1', 'F2', 'F3', 'F15', 'F30', 'F42', 'F31', 'F29', 'F35', 'F7', 'F6', 'F19', 'F25', 'F26', 'F8'], 'T1_composed_limit_dropped': ['F19', 'F26'], 'T1_force_raised': ['F7'], 'T1_substituted_reading': ['F26'], 'T1_outside_cards': ["'citation faithfulness' (T1-1): in no field source; the archive's 'RAG faithfulness' (O725-01) not surfaced", "'GPT-4' given the headline figure (T1-5): the field gives it to a fine-tuned GPT-3.5 (F7)"], 'T1_available_not_composed': ['F4', 'F5', 'F9', 'F10', 'F11', 'F12', 'F13', 'F14', 'F16', 'F17', 'F18', 'F20', 'F21', 'F22', 'F23', 'F24', 'F27', 'F28', 'F32', 'F33', 'F34', 'F36', 'F37', 'F38', 'F39'], 'own_page_not_surfaced': ['F40', 'F41', 'F42', 'F43'], 'rule': "a field claim counts as composed when T states it at its source's grain or coarser; a claim T states with its qualifier removed is listed under limit dropped as well as composed", 'LB_vs_LBA_added': ['CAP-1-01', 'CAP-1-02', 'CAP-1-03', 'CAP-1-04', 'CAP-1-05', 'CAP-1-06', 'CAP-1-07', 'CAP-1-08', 'CAP-1-09', 'PE-01', 'PE-02', 'PE-03', 'PE-04', 'PE-05', 'PE-06', 'PE-07', 'PE-08', 'PE-09', 'PE-10', 'PE-11', 'PE-12', 'PE-13', 'PE-14', 'PE-15', 'PE-16', 'PE-17', 'PE-18', 'PE-19', 'PE-20', 'PE-21', 'O716-01', 'O716-02', 'O716-03', 'O716-04', 'O716-05', 'O725-01', 'O725-02', 'O725-03', 'O725-04', 'O725-05', 'O725-06', 'O95-01', 'O141-01', 'O141-02', 'O1611-01', 'O1680-01', 'O1695-01', 'O1695-02', 'O1705-01']}
O716-02 absent from T: support stated, the failure to attempt attribution not distinguishedO716-02O725-02 absent from T: a faithful (supported) answer can still strip authorial framework membershipO725-02PE-13 absent from T: support by evidence composed as the whole of attributionPE-13O141-02 absent from TO141-02O1695-02 absent from T: local support not read alongside the identity of the objectO1695-02PE-12 kept by silence in T (CAP-1-03); the distinction itself not composedPE-12CAP-1-04 missing finding: the makers named only in the cardsCAP-1-04CAP-1-09 missing finding: no card cites the census recordCAP-1-09PE-15 absent from T: the constituent datasets' credit (F28) and the census's unchecked statusPE-15Candidates are found by string; admission is by reading.
Lee Sharks · Crimson Hexagonal Archive · register v1.36, 2026-10-27. Built by scripts/build_non.py from the files linked above; it writes nothing back. Working, not frozen.