Human Feedback Types
partialRubric Rating
Directly usable for protocol triage.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
HFEPX · Eval paper review
Alina Avanesyan, Alexey Boldyrev, Liqun Deng, Denis Derkach +9 more
Published
Nov 18, 2026
Citations
0
Trust level
Low
Usefulness score
40/100 (Low)
Extraction confidence
45% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 18, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
Use this page for context, then validate protocol choices against stronger HFEPX references before implementation decisions.
Best use
Background context only
Use if you need
Background context only.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
The available metadata is too thin to trust this as a primary source.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run. Existing benchmarks either match a symbolic answer against a key or, where they require executable work, score it by unit tests, by a rubric, or by position on a competition leaderboard. None of these is the criterion by which a field decides that one published method beats another. STEMBench adopts that criterion directly. Each of its twelve research problems in high-energy physics, astrophysics and neuroscience is scored by its own field's figure of merit, and each comes with two measured anchors: a submission that uses no domain knowledge, and an expert reference reproducing a published method, both obtained by running code shipped with the benchmark. The interval between them states how much of a problem is crossed by scientific insight rather than by engineering. Across eight frontier models, task-level wins and domain-level leadership dissociate: a model that wins five of the twelve tasks leads no domain mean. In the high-effort cross-model comparison, at least one model's mean score exceeds the expert anchor on seven of twelve tasks. The remaining five span uncertainty estimation, latent and causal inference, and cross-site clinical classification. Numerical scores and official-submission validity capture different aspects of performance and are reported separately. We release the tasks, graders, anchors and harness.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
Rubric Rating
Directly usable for protocol triage.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
None explicit
Validate eval design from full paper text.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
Not reported
No explicit QC controls found.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
Not extracted
No benchmark anchors detected.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
Not extracted
No metric anchors detected.
"Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
Scientific problems have no answer key, so evaluating an agent means deciding what counts as a better solution before any agent is run.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
Detected: Rubric Rating
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.