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

Does Datalab extract the same field from documents laid out differently?

Datalab returned the correct identifier, subtotal, tax and total due from all three differently laid-out receipts, with the same four-field schema. That included a receipt whose number was relabelled as a work order number and moved to a top-left box, returned as GLR-98213 with $227.33 due, and a single-column receipt with USD amounts, returned as SPD-2026-0714 with USD 157.50 due, each equal to the printed value.

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.

Same field across three layoutsPassEvidence
What we sent

In Datalab Forge's Extract playground, we chose Balanced mode, entered one four-field schema and ran all three receipts together with Run all (3); nothing was typed as a message.

Input 1Document (PDF)
Input PDF: the baseline receipt, number at top right, total $90.10
Open the PDF ↗
Input 2Document (PDF)
Input PDF: the invoice with its number labelled work order number, boxed top left
Open the PDF ↗
Input 3Document (PDF)
Input PDF: the single-column receipt with amounts written as USD values
Open the PDF ↗
Input 4File (JSON)
Extraction schema: the four required text fields used for all three receipts
JSON
{
  "type": "object",
  "properties": {
    "identifier_number": {
      "type": "string",
      "description": "The receipt or work order number that uniquely identifies this document"
    },
    "subtotal": {
      "type": "string",
      "description": "The subtotal amount before tax"
    },
    "tax": {
      "type": "string",
      "description": "The tax amount"
    },
    "total_due": {
      "type": "string",
      "description": "The total amount due"
    }
  },
  "required": ["identifier_number", "subtotal", "tax", "total_due"]
}
Open the JSON file ↗
What the tool returned

Returned JSON for the single-column receipt: SPD-2026-0714 and its USD amounts

Copied from Output file 1 (JSON)

JSON
{
  "identifier_number": "SPD-2026-0714",
  "identifier_number_citations": [
    {
      "block": "/page/0/Text/7",
      "page": 0,
      "text": "SPD-2026-0714",
      "offset": 0,
      "length": 13,
      "score": 1,
      "bbox": [134, 501, 344, 535]
    }
  ],
  "identifier_number_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Text/7"],
    "verification": {
      "status": "PASS",
      "feedback": "The receipt number is shown in /page/0/Text/7. Conclusion: the value at /page/0/Text/7 agrees with the extraction."
    }
  },
  "subtotal": "USD 150.00",
  "subtotal_citations": [
    {
      "block": "/page/0/Table/12",
      "page": 0,
      "text": "USD 150.00",
      "offset": 61,
      "length": 10,
      "score": 1,
      "bbox": [1045, 887, 1185, 916]
    }
  ],
  "subtotal_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/12"],
    "verification": {
      "status": "PASS",
      "feedback": "The subtotal amount is shown in /page/0/Table/12. Conclusion: the value at /page/0/Table/12 agrees with the extraction."
    }
  },
  "tax": "USD 7.50",
  "tax_citations": [
    {
      "block": "/page/0/Table/12",
      "page": 0,
      "text": "USD 7.50",
      "offset": 112,
      "length": 8,
      "score": 1,
      "bbox": [1350, 1048, 1461, 1079]
    }
  ],
  "tax_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/12"],
    "verification": {
      "status": "PASS",
      "feedback": "The tax amount is shown in /page/0/Table/12. Conclusion: the value at /page/0/Table/12 agrees with the extraction."
    }
  },
  "total_due": "USD 157.50",
  "total_due_citations": [
    {
      "block": "/page/0/Table/12",
      "page": 0,
      "text": "USD 157.50",
      "offset": 131,
      "length": 10,
      "score": 1,
      "bbox": [1286, 1108, 1461, 1144]
    }
  ],
  "total_due_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/12"],
    "verification": {
      "status": "PASS",
      "feedback": "The total due is shown in /page/0/Table/12 and reconciles with the subtotal plus tax. Conclusion: the value at /page/0/Table/12 agrees with the extraction."
    }
  }
}
Open the JSON file ↗

Returned JSON for the work-order invoice: GLR-98213, $210.00, $17.33, $227.33

Copied from Output file 2 (JSON)

JSON
{
  "identifier_number": "GLR-98213",
  "identifier_number_citations": [
    {
      "block": "/page/0/Text/4",
      "page": 0,
      "text": "GLR-98213",
      "offset": 0,
      "length": 9,
      "score": 1,
      "bbox": [161, 344, 330, 378]
    }
  ],
  "identifier_number_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Text/4"],
    "verification": {
      "status": "PASS",
      "feedback": "The work order number is shown in /page/0/Text/4. Conclusion: the value at /page/0/Text/4 agrees with the extraction."
    }
  },
  "subtotal": "$210.00",
  "subtotal_citations": [
    {
      "block": "/page/0/Table/16",
      "page": 0
    }
  ],
  "subtotal_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/16"],
    "verification": {
      "status": "PASS",
      "feedback": "The invoice table lists the subtotal in /page/0/Table/16. Conclusion: the value at /page/0/Table/16 agrees with the extraction."
    }
  },
  "tax": "$17.33",
  "tax_citations": [
    {
      "block": "/page/0/Table/16",
      "page": 0,
      "text": "$17.33",
      "offset": 124,
      "length": 6,
      "score": 1,
      "bbox": [1362, 880, 1441, 909]
    }
  ],
  "tax_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/16"],
    "verification": {
      "status": "PASS",
      "feedback": "The invoice table lists sales tax in /page/0/Table/16. Conclusion: the value at /page/0/Table/16 agrees with the extraction."
    }
  },
  "total_due": "$227.33",
  "total_due_citations": [
    {
      "block": "/page/0/Table/16",
      "page": 0,
      "text": "$227.33",
      "offset": 142,
      "length": 7,
      "score": 1,
      "bbox": [1324, 943, 1441, 978]
    }
  ],
  "total_due_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/16"],
    "verification": {
      "status": "PASS",
      "feedback": "The invoice table lists the amount due in /page/0/Table/16. Conclusion: the value at /page/0/Table/16 agrees with the extraction."
    }
  }
}
Open the JSON file ↗

Returned JSON for the baseline receipt: RHS-70234, $85.00, $5.10, $90.10

Copied from Output file 3 (JSON)

JSON
{
  "identifier_number": "RHS-70234",
  "identifier_number_citations": [
    {
      "block": "/page/0/Text/10",
      "page": 0,
      "text": "RHS-70234",
      "offset": 0,
      "length": 9,
      "score": 1,
      "bbox": [134, 517, 287, 548]
    }
  ],
  "identifier_number_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Text/10"],
    "verification": {
      "status": "PASS",
      "feedback": "The receipt number is shown in block /page/0/Text/10. Conclusion: the value at /page/0/Text/10 agrees with the extraction."
    }
  },
  "subtotal": "$85.00",
  "subtotal_citations": [
    {
      "block": "/page/0/Table/15",
      "page": 0
    }
  ],
  "subtotal_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/15"],
    "verification": {
      "status": "PASS",
      "feedback": "The subtotal amount is shown in the receipt table at block /page/0/Table/15. Conclusion: the value at /page/0/Table/15 agrees with the extraction."
    }
  },
  "tax": "$5.10",
  "tax_citations": [
    {
      "block": "/page/0/Table/15",
      "page": 0,
      "text": "$5.10",
      "offset": 100,
      "length": 5,
      "score": 1,
      "bbox": [1377, 831, 1439, 860]
    }
  ],
  "tax_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/15"],
    "verification": {
      "status": "PASS",
      "feedback": "The tax amount is shown in the receipt table at block /page/0/Table/15. Conclusion: the value at /page/0/Table/15 agrees with the extraction."
    }
  },
  "total_due": "$90.10",
  "total_due_citations": [
    {
      "block": "/page/0/Table/15",
      "page": 0,
      "text": "$90.10",
      "offset": 112,
      "length": 6,
      "score": 1,
      "bbox": [1343, 896, 1439, 929]
    }
  ],
  "total_due_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Table/15"],
    "verification": {
      "status": "PASS",
      "feedback": "The total amount due is shown in the receipt table at block /page/0/Table/15. Conclusion: the value at /page/0/Table/15 agrees with the extraction."
    }
  }
}
Open the JSON file ↗
Expected vs. Found
✓Expected: The correct value of each field from every layout, with the same schema used for all three documents.Found: Returned identifier, subtotal, tax, total due: RHS-70234, $85.00, $5.10, $90.10; GLR-98213, $210.00, $17.33, $227.33; SPD-2026-0714, USD 150.00, USD 7.50, USD 157.50 - each as printed on its document.
Supporting proof
Proof 1Screenshot
Results screen: the baseline receipt beside its four extracted fields
Open original ↗
Proof 2Screenshot
Results screen: the work-order invoice beside its four extracted fields
Open original ↗
Proof 3Screenshot
Results screen: the single-column receipt beside its four extracted fields
Open original ↗
Proof 4Screenshot
Configuration panel: Balanced mode selected and the four-field schema
Open original ↗
Why this result

The test needed the correct value from each layout under one schema. All twelve returned values equal the printed ones, across the relabelled and moved identifier and the reformatted amounts. The result covers Balanced mode, one of the product's four extraction modes.

Also observed in this test case

Subtotal citations lack a position. On the baseline receipt and the work-order invoice, the subtotal's citation names only the table it sits in, with no text or position; every other field's citation carries both.

Subtotal citation points at another row. On the single-column receipt, the subtotal's citation points at the line-item row rather than the Subtotal row; both print USD 150.00, so the returned value is still correct.

Tested by Rugved Nichite · evidence dated 19 November 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
Datalab
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
Three one-page receipts of one kind: a baseline with the number at top right, one labelling it work order number in a top-left box, and a single-column one with USD amounts, all to be run with one unchanged four-field schema.
Extraction mode
Balanced
Tested
19 November 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.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityField Extraction →
ScenarioThe same field across layouts →
ToolDatalab →

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
20 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/datalab/the-same-field-across-layouts · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-19

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 1 · Document (PDF) ↗application/pdf · 54 KB
Output file 3 (JSON) ↗application/json · 2 KB
Input 2 · Document (PDF) ↗application/pdf · 8 KB
Output file 2 (JSON) ↗application/json · 2 KB
Input 3 · Document (PDF) ↗application/pdf · 7 KB
Output file 1 (JSON) ↗application/json · 2 KB
Input 4 · File (JSON) ↗application/json · 1 KB
Proof 1 · Screenshot ↗image/png · 204 KB
Proof 2 · Screenshot ↗image/png · 208 KB
Proof 3 · Screenshot ↗image/png · 194 KB
Proof 4 · Screenshot ↗image/png · 91 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)a96bbe1c5b22336e7b54169baf72b85e45eabf1312cd293a1821017b52fa85f7
Output file 3 (JSON)3b5d3f9c5f301b80e4968f097436110024f5019c6ff04057828196aa404f0ce5
Input 2 · Document (PDF)4a0b1754da9f52ce35a783d58f8e8a1b5e1353b5b992d5553122886f1cd4a638
Output file 2 (JSON)f2d8f6cf1affa5942c4a8d1a11f4d897feb2e908d3b01e2b5f6c7dd803c62d5f
Input 3 · Document (PDF)0276d246d69482340b53797f4eaa21831977cede22c8c8f14fc48dbf84757660
Output file 1 (JSON)4259f96190b8e437ad93bae621301ed911c7ffc452b100e90d70b9d5df30d810
Input 4 · File (JSON)7f325c9a186a66a43d911976494356c4227ae7563c25a035ce05ac83363ef20b
Proof 1 · Screenshot044e339900bb270913d91bdc390ad1be7ff8561e1522e83c302e8f08d8241bc6
Proof 2 · Screenshot0e7aaf57fd6aa062bfc1233f6db0db6a1ba0de8258de64b0c55d77ccf7517c9f
Proof 3 · Screenshota64091ce3a489088bfb443795f55ee04e6fa958c13042ca1fd68c4e50acabb4b
Proof 4 · Screenshotcd48d231e84a13a44027d8c5eeb9a684998f0d58cd635a40369bba3d4096785a