Back to Feed
Agents / Benchmarks & Evals

Benchmarking Reliability in Scientific AI Agents

Original: EarthVerse: Benchmarking Scientific Agents Across Dynamic Earth Systems and Natural Hazards

Listen to the summary

Uses a voice available on your device

Audio options
On this page 5 sections
Related concepts 3 concepts

Key Takeaways

  • EarthVerse assesses agents through package scoped investigations that require evidence selection and consistent physical reasoning.
  • The best performing system, Claude Fable 5, achieved a Combined Core score of 84.97.
  • While mean answer unit accuracy reached 84.65 percent, the Strict@95 metric peaked at only 34.81 percent, highlighting a massive gap in reliability.
  • Even top tier systems fail to maintain a consistent chain of logic across evidence, calculations, and interpretations in roughly two thirds of all investigations.

Summary & Methodology Analysis

EarthVerse provides a structured framework for auditing AI agents tasked with complex Earth system analysis. The methodology focuses on package scoped investigations, requiring agents to navigate and synthesize information from multiple sources rather than executing isolated, atomic tasks. By utilizing expert authored tasks and typed tools, the framework forces the agent to demonstrate provenance and transparency in its calculations, ensuring that the final output is backed by a declared set of observations and relevant layers. This approach treats the agent as a pipeline where each step must remain consistent with the previous one, including unit management and physical interpretation.

The benchmark evaluates a variety of systems using metrics like the Combined Core score and answer unit accuracy. Performance data reveals that while individual step accuracy is relatively high, achieving a mean of 84.65 percent, the agents struggle significantly with end to end rigor. Specifically, the Strict@95 score, which demands a high threshold for correctness across all components of an investigation, peaks at only 34.81 percent. Claude Fable 5 currently leads the benchmark with a Combined Core score of 84.97, demonstrating that while current models possess high factual retrieval capabilities, they are not yet fully autonomous in scientific reasoning workflows.

The primary technical limitation identified is the failure to maintain a consistent chain of logic. Current systems often complete individual operations successfully but experience critical errors or omissions when reconciling differences across evidence, scales, and units. As noted in the evaluation, even the strongest systems leave roughly two thirds of investigations with at least one consequential error. This underscores a systemic inability to preserve the integrity of a scientific chain throughout long running tasks, where errors in interpretation or physical calculations degrade the validity of the final result despite successful data retrieval.

Interactive System Flowchart

Click diagram to expand and zoom

Illustrative Implementation

A short sketch of the paper's core idea, not the authors' own code.

# Illustrative sketch (not from the paper)
import os
import json
import torch

# Load EarthVerse metadata (405 investigations, avg 34 files per event)
with open('earthverse_index.json') as f:
    index = json.load(f)  # contains list of investigations with file lists

def load_evidence(files):
    """Read all evidence files for one investigation"""
    data = []
    for fp in files:
        with open(fp) as f:
            data.append(f.read())
    return data

def compute_quantity(tensor_a, tensor_b):
    """Transparent calculation preserving provenance"""
    # Example: simple physics operation using PyTorch
    result = torch.mul(tensor_a, tensor_b)
    provenance = {'op': 'mul', 'inputs': [tensor_a.tolist(), tensor_b.tolist()]}
    return result, provenance

for inv in index['investigations'][:5]:  # iterate a few sample investigations
    evidence = load_evidence(inv['evidence_files'])
    # placeholder: extract numeric tensors from evidence (mocked here)
    a = torch.tensor([1.0, 2.0])
    b = torch.tensor([3.0, 4.0])
    qty, prov = compute_quantity(a, b)
    # Assemble answer unit with provenance chain
    answer = {
        'investigation_id': inv['id'],
        'calculation': qty.tolist(),
        'provenance': prov,
        'evidence_used': inv['evidence_files']
    }
    print(json.dumps(answer))

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the goal of EarthVerse?

EarthVerse is a benchmark designed to measure and diagnose the reliability of scientific agents when they perform complex investigations related to Earth systems and natural hazards.

Q2. How does EarthVerse test an AI agent?

It tests agents through package scoped investigations where the agent must identify compatible evidence from multiple files, execute calculations, and preserve provenance in the final answer.

Q3. Which model performed the best in this benchmark?

Claude Fable 5 achieved the highest Combined Core score of 84.97.

Q4. What is the difference between mean answer-unit accuracy and the Strict@95 score?

The mean answer unit accuracy measures success on individual components at 84.65 percent, while the Strict@95 score measures overall investigation rigor, where the highest achieved score was only 34.81 percent.

Q5. What is the DORA component mentioned in the paper?

DORA is an approach that moves closer to an operational workflow by utilizing expert authored tasks, typed tools, and replayable reference calls while maintaining a declared set of observations.

Q6. Are current agents capable of performing fully reliable scientific investigations?

No. Even the strongest systems leave roughly two thirds of investigations with at least one consequential error or omission.

Q7. Does the paper prescribe a specific order for tool usage?

No, the evaluation uses process rubrics that do not prescribe a fixed tool use order.

Q8. What specific failure points does the benchmark track?

The benchmark tracks failures across evidence access, tool selection, memory, reasoning, and interaction.

Q9. How many systems were tested in this benchmark?

The benchmark tested 25 systems.

Flag an issue

What is wrong with this summary?

What is wrong?