MétaCan
Menu
Back to cohort

On Evaluation of Document Classification with RVL-CDIP

2023· article· en· W4386566652 on OpenAlexfundno aff
Stefan Larson, Gordon Lim, Kevin Leach

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicImbalanced Data Classification Techniques
Canadian institutionsnot available
FundersAtomic Energy of Canada Limited
KeywordsBenchmarkingBenchmark (surveying)Computer scienceScope (computer science)Resource (disambiguation)Artificial intelligenceTask (project management)Machine learningInformation retrievalData miningPattern recognition (psychology)EngineeringBusiness

Abstract

fetched live from OpenAlex

The RVL-CDIP benchmark is widely used for measuring performance on the task of document classification.Despite its widespread use, we reveal several undesirable characteristics of the RVL-CDIP benchmark.These include (1) substantial amounts of label noise, which we estimate to be 8.1% (ranging between 1.6% to 16.9% per document category); (2) presence of many ambiguous or multi-label documents; (3) a large overlap between test and train splits, which can inflate model performance metrics; and (4) presence of sensitive personally-identifiable information like US Social Security numbers (SSNs).We argue that there is a risk in using RVL-CDIP for benchmarking document classifiers, as its limited scope, presence of errors (state-of-the-art models now achieve accuracy error rates that are within our estimated label error rate), and lack of diversity make it less than ideal for benchmarking.We further advocate for the creation of a new document classification benchmark, and provide recommendations for what characteristics such a resource should include. Model (Reported by) Modality Accuracy

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.027
metaresearch head score (Gemma)0.061
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.027
Threshold uncertainty score0.140

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0270.061
Meta-epidemiology (narrow)0.0030.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0060.006
Science and technology studies0.0020.001
Scholarly communication0.0050.006
Open science0.0040.004
Research integrity0.0030.003
Insufficient payload (model declined to judge)0.0030.005

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.075
GPT teacher head0.341
Teacher spread0.265 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations13
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicImbalanced Data Classification TechniquesFrench-language works237,207