Can FutureSmart Document Intelligence repair a record?
FutureSmart Document Intelligence fails this repair task. It could not add a new line item or find a delete option, and the read-back stayed at the same ten Blackwood items.
1 of 1 test case failed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Add one member and remove oneFailEvidence
We typed a new item into the Blackwood invoice and right-clicked a line item to look for delete controls.
{ "object_id": "a24ef21c-747c-4a35-b8e5-442ec07b32ef", "file": "main_invoice_multipage_blackwood.pdf", "line_items_0_description": "Retail Shelving Unit - Steel, 5-Tier", "line_items_1_description": "Checkout Counter - Laminate Top", "line_items_remaining_description": [ "Security Tag Deactivator - Handheld", "Price Label Printer - Thermal", "Shopping Basket - 20L, Set of 10", "Storeroom Pallet Racking - 4-Bay", "Barcode Scanner - Wireless", "Receipt Paper Roll - Case of 50", "Mannequin - Adjustable, Full Body", "Display Signage Kit - Window Set" ] }
Exported line-item set with ten unchanged items
Copied from Output file (JSON), lines 1–16
Open the JSON file ↗| ✗ | Expected: The added member should appear, the removed member should be gone, and the other members should stay unchanged.Found: The set stayed at ten items; the new entry could not be entered, no delete option appeared, and the other items stayed unchanged. |
The tool’s response is printed above, under What the tool returned. Show this screenshot
Open original ↗The task required one member added and one removed. The product offered no add, delete, or edit control for line items, so the new item could not be entered and no delete option appeared; the set stayed unchanged.
No value-edit endpoint. The API reference documents no endpoint for editing extracted values; only field-definition endpoints are documented.
The Blackwood edit-attempt capture shows only the after state; the typing and right-click are not visible.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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 row says which 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 row 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | Review and Correction → | |
| Scenario | Repair a record → | |
| Tool | FutureSmart Document Intelligence → |
Global scenario definition → · Global capability definition →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.