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

Can Docsumo choose the right value when the definition is supplied?

Docsumo selected the value specified by the supplied definition. It returned the shipment reference rather than the more prominent invoice number.

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.

Definition overrides the prominent numberPassEvidence
What we sent

Input · Definition of the field reference_number: “The consignment reference number — the identifier tied to the physical shipment. This is NOT the invoice number, even though the invoice number appears more prominently (labelled, and repeated in the footer of every page).”

InputDocument (PDF)
Input PDF: freight invoice with an invoice number and a shipment reference
Open the PDF ↗
What the tool returned
JSONthe whole file · copied lines 1–11
{
  "Invoice Details": {
    "reference_number": {
      "value": "CFS-CN-40821",
      "position": [1359, 351, 1514, 381],
      "confidence": 1,
      "review_required": false
    }
  }
}

Structured output: the extracted shipment reference

Copied from Output file (JSON), lines 1–11

Open the JSON file ↗
Expected vs. Found
✓Expected: Return the shipment reference selected by the supplied definition, not the more prominent invoice number.Found: The results screen and structured output returned the consignment reference; the supplied definition required the shipment reference, not the invoice number.
Supporting proof
Proof 1Screenshot
Results screenshot: the shipment reference returned beside the invoice
Open original ↗
Proof 2Screenshot
Field settings screenshot: the supplied definition beside the extraction result
Open original ↗
Why this result

The definition and result are visible together: Docsumo chose the shipment reference, as required, rather than the invoice number repeated in every page footer. The document itself supplies no rule for choosing between them.

Tested by Rugved Nichite · evidence dated 5 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
Docsumo
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The Calderwood Freight invoice paired a more prominent invoice number with a shipment reference. The reference number schema field used the supplied definition in an Extraction block; Reasoning Instructions were off.
Block type
Extraction
Reasoning instructions
off
Tested
5 October 2026 · Rugved Nichite

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.

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
17 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/docsumo/the-value-needs-a-supplied-definition · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-05

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 · 118 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 0 KB
Proof 1 · Screenshot ↗image/png · 131 KB
Proof 2 · Screenshot ↗image/png · 135 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1bcc6c7b945956c5b6f5a87d223ed3d578a62aa2c56c5fc1e3abedb4cc4de72e
Output file (JSON)e83c456c31e180a931266ad10db6b2104bfedab6d4ffae18e37b3dc68572a144
Proof 1 · Screenshot836a784683a032e0a2906752f3ce116669220ed7f93278ec0b16fdedc06e92aa
Proof 2 · Screenshot74743156afbe18d7af47e713e2fdf2dac2f1c89165f4eafa39d1193ba27fdf65