Explore more topics
Published model evaluations

Catch errors a successful research script can miss

See ten filing transactions become nineteen extracted rows, then follow how independent reviewers reduce their findings. Compare the actual published recall and consistency results.

As of 2026-08-08

Jump to a section

TL;DR

Luna and Hy3 each found 83.1% of labeled defects in the August 2026 artifact review study. Luna repeated its grade on 19 of 23 artifacts, versus Hy3's 18 and MiniMax's 16. That supports a small consistency preference in this sample, with tied recall. A separate public filing example shows why successful extraction can still contain duplicate rows and reversed trades. Reducer quality remains limited by the findings its reviewers supply.

Follow an error through the review

Ten transactions in the cited source filing became nineteen extracted transactions, and a Disney sale became a purchase
Published Pelosi extraction example. It explains errors to inspect; the publication does not identify it as a private benchmark artifact or a response from one of the three reducer models.
Step 1 of 4

Compare the rows with the source

The published Pelosi research checked 65 disclosure PDFs against 135 transactions read independently by eye. In the cited filing, a sliding-window regex returned 19 transactions instead of 10 and labeled a Disney sale as a purchase.

What you should see

Count the returned rows and check buy/sell direction against the filing. Plausible JSONL and a successful exit do not establish either match.

Four independent reviewers send nine findings to a reducer; six are upheld, three dropped and the displayed grade is B minus
Values from the published review-mechanism diagram. This illustrates how findings are reduced; it is separate from the 23-artifact model results.
Step 2 of 4

Reduce the findings before assigning a grade

The published review diagram sends four views of the artifact to independent reviewers. Nine findings reach the reducer; it drops three as noise, upholds six and displays B-minus.

What you should see

This is the published mechanism illustration. It is separate from the private benchmark set and does not identify a scored response from Luna, Hy3 or MiniMax.

Luna and Hy3 each find 83.1 percent of labeled defects, MiniMax 82.5 percent; repeat grades match on 19, 18 and 16 of 23 artifacts
Published August 8, 2026. Defect recall and repeated-grade agreement are separate metrics. One extra repeated grade in 23 does not establish a universal advantage. No cost or latency is reported.
Step 3 of 4

Compare finding defects with repeating a grade

Luna and Hy3 tied at 83.1% reported defect recall. Their grades repeated on 19 and 18 of 23 artifacts respectively. MiniMax found 82.5% of defects and repeated its grade on 16 of 23.

What you should see

Luna has one more repeated grade than Hy3 in this sample. The reducer still depends on the defects its mappers supply, and these results provide no model costs or latencies.

Step 4 of 4

Inspect the extraction errors in Aurora

Open the prepared request in Aurora. It includes the example’s actual inputs, so you can ask about the part you want to check.

What you should see

Review the explanation against the evidence on this page. Account changes and research jobs require a separate decision.

What the result helps you choose

Read what the result helps you choose

Luna and Hy3 tied at 83.1% defect recall. Luna repeated its grade on 19 of 23 artifacts, Hy3 on 18 and MiniMax on 16. That one-artifact difference supports a consistency preference in this sample; the table publishes no model cost or latency.

Task and tested input

Read task and tested input

Judge defects in delivered research artifacts, including code and validation evidence.

  1. Instruction in brief (task summary)

    Given mapper findings, decide which defects are supported and assign a grade. A public example checks 65 Pelosi disclosure PDFs against 135 transactions read independently by eye.

Published results

Scale: 0 to 83.1 % · zero baseline

Defects found

  • openai/gpt-5.6-luna83.1%
  • tencent/hy383.1%
  • minimax/minimax-m382.5%

23 hand-labeled artifacts covering 14 task types; 3 reducer models in the public table. Published 2026-08-08. Values retain their original units and grading scale.

Show the table · 3 rows, 3 columns

Scroll sideways to compare all columns. Select a heading to sort.

openai/gpt-5.6-luna83.1%19 of 23
tencent/hy383.1%18 of 23
minimax/minimax-m382.5%16 of 23

23 hand-labeled artifacts covering 14 task types; 3 reducer models in the public table. Published 2026-08-08. Values retain their original units and grading scale.

Calculate the decision from the measured rows

Scale: 0 to 83.1 % · zero baseline

Defects found

  • openai/gpt-5.6-luna83.1%
  • tencent/hy383.1%
Show the table · 2 rows, 3 columns

Scroll sideways to compare all columns. Select a heading to sort.

openai/gpt-5.6-luna83.1%19 of 23
tencent/hy383.1%18 of 23

Both reducers found 83.1% of the hand-labeled defects. Luna repeated its grade on 19/23 reruns (82.61%), compared with Hy3's 18/23 (78.26%): one additional agreement in 23 tests. The measurable difference is consistency in this sample; recall is tied.

The reducers receive the same mapper findings. A missed mapper finding cannot be recovered by choosing a stronger reducer. Inspect the actual duplicate-row case on this page before interpreting the aggregate score as end-to-end review coverage.

How the runs worked

Read the test procedure

23 hand-labeled artifacts covering 14 task types; 3 reducer models in the public table

Map/reduce artifact grader versus independently hand-labeled defects

  1. Step 1

    Label defects in 23 artifacts across 14 task types.

  2. Step 2

    Give each reducer exactly the same mapper findings.

  3. Step 3

    Compare defect recall and whether rerunning keeps the same grade.

How to read the measurements

Read how to read the measurements
  1. Grading and valid output

    Defect recall is the share of hand-labeled defects found. Repeated-grade agreement counts artifacts assigned the same grade on a repeat; agreement alone does not prove correctness.

  2. Cost

    This comparison table has no per-model billing column.

  3. Time

    This table publishes no per-model latency.

  4. Mapper / reducer

    Mappers inspect parts of an artifact independently. The reducer combines their findings and assigns the final grade.

Sample and scope

Read sample and scope

A reducer cannot discover a defect absent from its mapper inputs. These results do not establish end-to-end recall for every arbitrary artifact.

GPT 5.6 Luna and Tencent Hy3 tie on reported defect recall (83.1%). Their repeated-grade counts differ by one in 23 tests; that is not evidence of a universal review advantage.

This is a task-specific snapshot. Current grader defaults and newer model versions are not inferred from an August publication.

Read the original evidence

Read read the original evidence

Aurora product context

Published Aurora workflow recording showing a trading-strategy request and the agent loop
The August article shows this Aurora product workflow. The recording provides product context rather than an individual benchmark response.
See the broader product workflow

This August recording shows the broader Aurora agent workflow. The task explanations above describe each evaluation; its private conversations and complete system prompts remain private.

Continue exploring

Discussion

Sign in or create a free account to join the discussion.

No comments yet.

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.