Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

Benchmarking LLM abilities on postdoc-level natural science problems

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

Should you rely on this paper?

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.

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.

Human feedback signal
Detected
From extracted signals
Evaluation signal
Weak or implicit
Validate from full paper
Usefulness for eval research
40/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

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.

What we could verify

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.

Human Feedback Types

partial

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."

Evaluation Modes

missing

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."

Quality Controls

missing

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."

Benchmarks / Datasets

missing

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."

Reported Metrics

missing

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."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
Yes
Feedback types
Rubric Rating
Rater population
Not reported
Unit of annotation
Multi Dim Rubric (inferred)
Expertise required
Medicine, Coding
Evaluation details
Evaluation modes
None
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

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.

Key takeaways

  • 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.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Contribution summary

  • 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.

Why it matters for eval

  • 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…

Researcher checklist

  • 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.