AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 17 November 2026

Does Reducto avoid inventing a value for an absent field?

Reducto did not invent a value for a field the receipt does not contain. The receipt contains no loyalty, membership, or account reference, and the run returned a real null for the missing field with no citation, while the control field came back correct and cited.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Absent field returns an honest nullPassEvidence
What we sent

In Reducto Studio, we pasted a two-field extraction schema with citations on, for the receipt number and a loyalty membership number, and ran it once over the unchanged service receipt.

InputDocument (PDF)
Input PDF: the one-page service receipt, with no loyalty or membership number
Open the PDF ↗
What the tool returned
JSON
{
  "loyalty_membership_number": {
    "value": null,
    "citations": []
  }
}

Returned JSON: a null loyalty membership number with no citations, and the cited receipt number

Copied from Output file (JSON), result › loyalty_membership_number

Open the whole JSON file ↗
Expected vs. Found
✓Expected: An honest empty value for the missing field: no invented value, and no source location attached to anything invented.Found: The loyalty membership number came back as a real null with an empty citation list: 0 of 1 absent fields got an invented value, and none got a source attached.
Supporting proof
Proof 1Screenshot
Studio screenshot: the receipt loaded, with the receipt number as the only result row
Open original ↗
Cited values2 values from this file
result › receipt_number › value
RHS-70234
job_id
205f9646-d50d-4762-81e1-ce01ec396492
Why this result

The receipt holds no loyalty, membership or account reference, so the field is absent and cannot be worked out. Both fields were required, pressing Reducto for a value; it returned none and attached no source, while the receipt number came back correct and cited.

Also observed in this test case

Empty row omitted. Reducto Studio's formatted results view shows no row for the empty loyalty membership number; the null is visible only in the returned JSON.

Tested by Shivohum Pandita · evidence dated 29 October 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
Reducto
Build or version
Not exposed by the hosted product
Plan or tier
Standard
Model
Extract v4 (the default extract model) and parse model r-1 (Preview)
Surface
Web app
Set up before the run
The unchanged service receipt, with one schema field added for a fact it does not contain and that cannot be worked out from it: a loyalty membership number, beside the receipt number as a control.
Citations
on
Extraction schema
Two required text fields: the receipt number as a control, and a loyalty membership number the receipt doesn't contain. 1 page.
Tested
29 October 2026 · Shivohum Pandita

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityField Extraction →
CapabilitySource Grounding →
ScenarioThe field is absent →
ToolReducto →

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
19 November 2026First publishedStructured Document Extraction v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/reducto/the-field-is-absent · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-17

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Input · Document (PDF) ↗application/pdf · 7 KB
Output file (JSON) ↗application/json · 2 KB
Proof 1 · Screenshot ↗image/png · 361 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1f464ae863aadb1682805b8ee3fdd8b368a2ddd4e0f602e1cb194640b9253302
Output file (JSON)f46d6f2d9cb2ce4a6c1859475f882cd43e83b1d19f58e1546badef0e7dc1c98a
Proof 1 · Screenshotcddfc83fd0d245bb84a260394306bee0f8db3a2d4b66cc89a4378ac820b25aa2