Benchmark Intake

Benchmark intake is the first pass for deciding what a reported result can actually support. It turns a paper’s score into a checked contract over data, task, split, metric, allowed information, and reporting rules.

where is data, is the task, is the split, is the metric set, is allowed data/resources/information, and is the reporting rule.

Intake Fields

FieldQuestionRoute
DataWhat dataset version, source, filtering, and preprocessing define the examples?Dataset card
TaskWhat input-output mapping is evaluated?Tasks, Task specification
Example unitWhat counts as one prediction or one generated sample?Example unit
Split unitWhat unit is prevented from crossing train, validation, and test?Split unit, Dataset split contract
Split axisIs the held-out axis row, scaffold, protein family, pair, source, time, or multiple axes?Dataset split contract
MetricWhat number decides success, and what diagnostics are secondary?Metric selection
Claim contractWhat narrow claim does the score actually support?Benchmark claim contract
BaselineWhat simple or established method makes the score meaningful?Baseline
Allowed informationWhat training data, templates, retrieval corpus, prompts, or preprocessing are allowed?Test-set contamination
ReportingAre uncertainty, paired comparisons, invalid outputs, and subgroup failures reported?Evaluation protocol

Claim Mapping

Reported ResultSupported Only If
Higher aggregate scoremetric, split, model-selection rule, and uncertainty are comparable
Better OOD generalizationheld-out units match the claimed deployment shift
Better molecular screeningscaffold/source split, early enrichment, negative provenance, and baseline are stated
Better protein modelingsequence/family split, structure source, residue mapping, and template risks are stated
Better generative modelvalidity, diversity, novelty, utility, filtering, and sampling budget are stated
Better agent benchmarktask suite, tool access, verifier, human boundary, and failure accounting are stated
Better under constraintshard/soft constraint, repair/filtering, invalid denominator, and deployment-available constraints are stated

Evidence Rule

A benchmark score is a finite-sample estimate:

Here is the per-example metric, is the aggregation rule, and is the fixed model selected before final test evaluation.

If , preprocessing, threshold, prompt, or filtering choices are selected using the test set, the result is no longer an untouched final estimate.

Failure Checks

  • Is the benchmark testing interpolation rather than the claimed shift?
  • Are invalid predictions counted in the denominator?
  • Are repeated test submissions or leaderboard feedback part of the selection loop?
  • Could pretraining, retrieval, templates, or prompt examples contain test items?
  • Are split axes strong enough for the claimed deployment shift?
  • Is the baseline too weak to expose a dataset shortcut?
  • Does one aggregate hide per-target, per-scaffold, per-source, or per-domain failures?
  • Are uncertainty intervals or paired comparisons needed to interpret the reported gain?

Molecular Modeling-Specific Checks

  • Molecule benchmarks: standardization, scaffold grouping, decoy provenance, and activity cliffs.
  • Protein benchmarks: sequence identity, family split, structure source, residue indexing, and homolog leakage.
  • Protein-ligand benchmarks: ligand scaffold, protein family, complex pair, pocket definition, and template leakage.
  • Assay benchmarks: endpoint, unit, threshold, censoring, source, and assay harmonization.
  • Multi-axis benchmarks: state whether ligand, protein, pair, assay/source, and time axes are held out independently or jointly.