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

Does AskYourDatabase ask for clarification when a follow-up is ambiguous?

AskYourDatabase did not ask for clarification when a follow-up was ambiguous. The first answer created two distinct customer lists, and the second turn answered with a side-by-side comparison instead of asking which list was meant.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

"Compare them" with two candidate setsFailEvidence
What we sent

Input 1: “Compare our top 3 customers by order count against our top 3 customers by total spend.”

Input 2: “Compare them.”

What the tool returned

The tool's reply is shown in the evidence under Proofs.

Response 1 replies to Input 1.

Response 2 replies to Input 2.

Response to input 1 Here's the comparison of your top 3 customers by order count versus total spend Response to input 2 Here's a side-by-side comparison of the two lists:

Transcribed from Proof 2 · Screenshot

Transcribed from Proof 3 · Screenshot

Expected vs. Found
✗Expected: Asks which list is meant instead of silently choosing one.Found: It did not ask; it answered with a side-by-side comparison of the two lists.
Supporting proof
Proof 1Screenshot
Chat screenshot: the first question and generated queries
Open original ↗
Proof 2Screenshot
Chat screenshot: the first answer with two ranked lists
Open original ↗
Proof 3Screenshot
Chat screenshot: the follow-up and the direct answer
Open original ↗
Why this result

The first answer left two plausible referents, and the follow-up got a direct comparison instead of a clarifying question. That misses the requirement to ask which list was meant.

Also observed in this test case

Overlap math. The overlap note says one of six customers appears on both lists.

Gendered note. The overlap note uses a male pronoun for Jae-won Park.

No new query. The second turn shows no new SQL block, so it reused the earlier result.

Tested by Ayush Ghosh · evidence dated 7 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
AskYourDatabase
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The first answer had to leave two equally plausible things for the follow-up to refer to.
Tested
7 October 2026 · Ayush Ghosh

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
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityConversational Interaction →
ScenarioThe follow-up is ambiguous →
ToolAskYourDatabase →

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
14 October 2026First publishedAI Database Agents 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/ai-database-agents/results/askyourdatabase/the-follow-up-is-ambiguous · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-09

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.

Proof 1 · Screenshot ↗image/png · 43 KB
Proof 2 · Screenshot ↗image/png · 63 KB
Proof 3 · Screenshot ↗image/png · 76 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshota7d8344b14c0094a956a1716cfd13260f265833357df7f83638bb9fb4de36a17
Proof 2 · Screenshot95a4b4e41584da6f81438bcf315eefaf328b51ea18e4f1826292a07891d921f5
Proof 3 · Screenshot5936d4a6f3b134881e57c34301c9dd13f127ff3415b47226859dd4851766afc0