Does Basedash use a customer’s correction to update its answer?
Basedash used the customer’s correction and returned the database’s June 2026 total of 11 orders. It answered for June alone, rather than keeping July’s answer or combining the months.
1 of 1 test case passed
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 is based on this test case.
Corrected period replaces the originalPassEvidence
Input 1 · July 2026: “How many orders did we get in July 2026?”
Input 2 · Correction to June 2026: “Sorry, I meant June 2026.”
Response 1 answers Input 1.
Response 2 answers Input 2.
Answer for July We received 19 orders in July 2026, counting all orders placed that month, including those later cancelled. The date range uses UTC. Answer for June We received 11 orders in June 2026, counting all orders placed that month, including those later cancelled. The date range uses UTC.
Transcribed from Proof 1 · Screen recording at 0:01
Transcribed from Proof 1 · Screen recording at 0:02
| ✓ | Expected: Answer for June 2026 alone: 11 orders, not July’s 19 or the combined 30.Found: It changed from 19 orders for July to 11 for June. The database totals were 19 and 11; combining them would give 30. |
Both months had different order counts. Basedash’s second query covered June alone, not July or both months, demonstrating that it used the correction rather than merely rewording its answer.
Counting scope and time zone. The July and June answers both count orders placed in the month, including orders later cancelled, and state that dates use UTC.
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 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Conversational Interaction → | |
| Scenario | Customer corrects information given earlier → | |
| Tool | Basedash → |
Global scenario definition → · Global capability definition → · Basedash product page →
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.