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

Can Datalab derive a value that is not printed in a document?

Datalab calculated a fuel cost that was not printed in the invoice. It returned £81.00 from 450 miles at £0.18 per mile, the exact result of multiplying the two values.

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.

Derived value from two present valuesPassEvidence
What we sent

We ran the three-page Calderwood Freight invoice once through Extract in Datalab’s Forge playground, using a schema that requested the fuel cost as distance multiplied by fuel rate.

Input 1Document (PDF)
Input PDF: the three-page invoice with distance and fuel rate, but no calculated fuel cost
Open the PDF ↗
Input 2File (JSON)
Schema file: three required text fields and instructions to calculate the fuel cost
JSON
{
  "type": "object",
  "properties": {
    "distance_miles": {
      "type": "string",
      "description": "The distance of the route, in miles, as stated on the invoice."
    },
    "fuel_rate_per_mile": {
      "type": "string",
      "description": "The fuel rate per mile, labelled 'FUEL RATE' on the document, including currency. The value may be a whole number or a decimal number - if the number in the document is in decimal form, the extraction should give the value in decimal, exactly as mentioned in the document."
    },
    "total_fuel_cost": {
      "type": "string",
      "description": "The total fuel cost - calculated as the distance in miles multiplied by the fuel rate per mile. This value does NOT appear anywhere in the document; you must compute it from distance_miles x fuel_rate_per_mile."
    }
  },
  "required": ["distance_miles", "fuel_rate_per_mile", "total_fuel_cost"]
}
Open the JSON file ↗
What the tool returned
JSON
{
  "distance_miles": "450 miles",
  "distance_miles_citations": [
    {
      "block": "/page/0/Text/10",
      "page": 0,
      "text": "450 miles",
      "offset": 0,
      "length": 9,
      "score": 1,
      "bbox": [1366, 504, 1458, 530]
    }
  ],
  "distance_miles_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Text/10"],
    "verification": {
      "status": "PASS",
      "feedback": "The route distance is stated in /page/0/Text/10. Conclusion: the value at /page/0/Text/10 agrees with the extraction."
    }
  },
  "fuel_rate_per_mile": "£0.18",
  "fuel_rate_per_mile_citations": [
    {
      "block": "/page/0/Text/12",
      "page": 0,
      "text": "£0.18",
      "offset": 0,
      "length": 5,
      "score": 1,
      "bbox": [135, 595, 189, 624]
    }
  ],
  "fuel_rate_per_mile_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": ["/page/0/Text/12"],
    "verification": {
      "status": "PASS",
      "feedback": "The fuel rate is stated in /page/0/Text/12. Conclusion: the value at /page/0/Text/12 agrees with the extraction."
    }
  },
  "total_fuel_cost": "£81.00",
  "total_fuel_cost_citations": [],
  "total_fuel_cost_meta": {
    "extraction_status": "EXTRACTED",
    "reasoning": null,
    "citations": [],
    "verification": {
      "status": "PASS",
      "feedback": "The document gives 450 miles in /page/0/Text/10 and £0.18 per mile in /page/0/Text/12; multiplying them gives the extracted total. Conclusion: the value at /page/0/Text/10 and /page/0/Text/12 agrees with the extraction."
    }
  }
}

Extraction output: the £81.00 fuel cost and Datalab’s explanation of the calculation

Copied from Output file (JSON)

Open the JSON file ↗
Expected vs. Found
✓Expected: A total fuel cost of £81.00, calculated from 450 miles at £0.18 per mile.Found: Datalab returned £81.00; multiplying the invoice’s 450 miles by £0.18 per mile gives the required £81.00.
Supporting proof
Proof 1Screenshot
Results screenshot: the two source values and the £81.00 calculated fuel cost
Open original ↗
Proof 2Screenshot
Configuration screenshot: Balanced mode and three required extraction fields
Open original ↗
Why this result

The invoice contained no printed total, and the schema explicitly required multiplication. Datalab returned the calculated £81.00 rather than either source value, so it supplied the derived value the task required.

Also observed in this test case

Sources behind the calculation. The distance and fuel-rate fields each cite their source on page 1. The fuel-cost total has no citation, while Datalab’s check explains which two cited source passages it multiplied.

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
The Calderwood Freight invoice had to state distance and fuel rate once each, omit the fuel-cost total, and make multiplication unambiguous. The extraction instructions had to request that total.
Extraction mode
Balanced
Extraction fields
three required text fields
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 value must be derived →
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-value-must-be-derived · 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 · 118 KB
Output file (JSON) ↗application/json · 2 KB
Proof 1 · Screenshot ↗image/png · 171 KB
Input 2 · File (JSON) ↗application/json · 1 KB
Proof 2 · Screenshot ↗image/png · 101 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)1bcc6c7b945956c5b6f5a87d223ed3d578a62aa2c56c5fc1e3abedb4cc4de72e
Output file (JSON)ffd7b51454dd059a3d391b0b383507b270369aa5b8b304a65c414c21dfa63a58
Proof 1 · Screenshotb7953040c32ccdc7f4eaa527d8a38cd71a2baca80783e49020ab76b661f91ba7
Input 2 · File (JSON)de0e3624b8cccfde282b6b661e94e7f827e69a4eeb503d0be4e5adc18032a17c
Proof 2 · Screenshotf819bde0a65c3a5bd74ec0606f69b33a385dbc84200621a1a15f8662b9de501a