{"observation":{"id":"ee22d062-e8e0-4ac9-8870-8cca0db9d8ec","tool":"dot","tool_name":"Dot","criterion":"result-readability","criterion_name":"Result Readability","criterion_definition":"Is the answer easy for a non-technical user to understand?","criterion_evidence_type":"transformation","criterion_rank_role":"decisive","criterion_rank_role_reason":"The point is to get usable answers from non-technical users, so the result has to be understandable. (3 of 3 judges)","scenario":"best-customers-with-unpaid-order-and-payment-method-follow-ups","scenario_name":"Best customers with unpaid-order and payment-method follow-ups","group_tag":"live-database-plain-english-queries","scenario_description":"A conversational multi-table customer analysis with follow-up questions. It asks for the best customers by both order volume and spend, then drills into unpaid orders for the top 3 and their usual payment methods. Designed to test ranking logic, join-heavy analysis, and follow-up context retention.","modality":"text","input_text":"Who are my best customers — the ones who order the most and spend the most?\n\nFollow-up 1: For the top 3 from that list — do any of them have unpaid orders?\n\nFollow-up 2: What payment methods do these top 3 usually use?","input_artifact_refs":[],"stresses":["ambiguous business term interpretation","multi-table joins","aggregation and ranking","follow-up context retention","scoping to a selected subset","payment behavior analysis"],"verdict":"mixed","score":null,"score_total":null,"note":"The follow-up answers are readable but terse: each is a one-line response, while the supporting table and SQL are pushed out of the main surface into Full logs.","evidence_state":"verified","source":null,"artifacts":[{"url":"https://cdn.futuresmart.ai/public/aidemos/e94fab739e414924b69bd67beb632d2f.png?v=1","role":"output","alt":null},{"url":"https://cdn.futuresmart.ai/public/aidemos/890888afc49e48b89d6dacc821125cf7.png?v=1","role":"output","alt":null}],"run_id":"af2abc96-3311-484b-a19d-854a2fdd2bf3","study_title":"Query Live Databases Using Plain English with AI","study_kind":"generation","research_task":"86b9y6c99","tested_at":null,"completeness":"input-and-output","input":{"state":"text","text":"Who are my best customers — the ones who order the most and spend the most?\n\nFollow-up 1: For the top 3 from that list — do any of them have unpaid orders?\n\nFollow-up 2: What payment methods do these top 3 usually use?","files":[],"modality":"text","stresses":["ambiguous business term interpretation","multi-table joins","aggregation and ranking","follow-up context retention","scoping to a selected subset","payment behavior analysis"]},"tool_page_slug":"dot","tool_url":"https://aidemos.com/tools/dot","permalink":"https://aidemos.com/evidence/ee22d062-e8e0-4ac9-8870-8cca0db9d8ec","api_url":"https://ai.aidemos.com/v1/observations/ee22d062-e8e0-4ac9-8870-8cca0db9d8ec"},"peers":[{"id":"6a130b11-3ffe-4dd1-b405-30c887af3d65","tool":"askyourdatabase","tool_name":"AskYourDatabase","verdict":"worked","score":null,"score_total":null,"note":"It presents the answer as clearly labeled ranking tables and customer-level payment summaries, with visual risk cues for unpaid or shipped orders.","artifact_count":4,"thumbnail":"https://cdn.futuresmart.ai/public/aidemos/ec0ed41fe3dd45b5b13b082d174be6b7.png?v=1","evidence_url":"https://aidemos.com/evidence/6a130b11-3ffe-4dd1-b405-30c887af3d65"},{"id":"8631a190-2b78-4695-a457-2b0ac633578c","tool":"basedash","tool_name":"Basedash","verdict":"worked","score":null,"score_total":null,"note":"The output stays readable for non-technical users, using compact tables and short summaries with explicit customer names and amounts.","artifact_count":3,"thumbnail":"https://cdn.futuresmart.ai/public/aidemos/b32adc19ccfc434bb534d9c3684fee55.png?v=1","evidence_url":"https://aidemos.com/evidence/8631a190-2b78-4695-a457-2b0ac633578c"},{"id":"cfe90f8a-a4cf-4c44-bafb-2e6f73ca7a40","tool":"definite","tool_name":"Definite","verdict":"worked","score":null,"score_total":null,"note":"It returns a ranked table with order counts, total spend, and average order value that is straightforward to read and scan.","artifact_count":1,"thumbnail":"https://cdn.futuresmart.ai/public/aidemos/852010033067408ba7a475364358d97f.png?v=1","evidence_url":"https://aidemos.com/evidence/cfe90f8a-a4cf-4c44-bafb-2e6f73ca7a40"},{"id":"492b3c4c-2b5a-42db-80b7-7b8f2464e506","tool":"draxlr","tool_name":"Draxlr","verdict":"struggled","score":null,"score_total":null,"note":"All three best-customer result tables keep customer_id as the lead column, so the output stays UUID-heavy and hard to scan.","artifact_count":3,"thumbnail":"https://cdn.futuresmart.ai/public/aidemos/ab41b8340d0a45188a25417725b1cede.png?v=1","evidence_url":"https://aidemos.com/evidence/492b3c4c-2b5a-42db-80b7-7b8f2464e506"},{"id":"ac7d4ce7-d376-4989-bb44-e8abdd293fbf","tool":"querio","tool_name":"Querio","verdict":"mixed","score":null,"score_total":null,"note":"The answer is usable, but it is less readable than it could be because the output centers customer UUIDs instead of human names.","artifact_count":4,"thumbnail":"https://cdn.futuresmart.ai/public/aidemos/a2212df102a643b4bd41951fd064776d.png?v=1","evidence_url":"https://aidemos.com/evidence/ac7d4ce7-d376-4989-bb44-e8abdd293fbf"}],"other_criteria":[{"id":"895073b3-49c1-4aad-967e-a214175ae66e","criterion":"ambiguity-handling","criterion_name":"Ambiguity Handling","rank_role":"decisive","verdict":"worked","score":null,"score_total":null,"note":"Faced with 'order the most and spend the most,' it did not silently choose one dimension; it built a combined equal-weight rank and explicitly surfaced the trade-off between all-around value and single-big-order spend.","artifact_count":2,"evidence_url":"https://aidemos.com/evidence/895073b3-49c1-4aad-967e-a214175ae66e"},{"id":"86d2a8b3-d9d0-4b8e-8e46-8bc17c6b5c6d","criterion":"business-insight","criterion_name":"Business Insight","rank_role":"decisive","verdict":"worked","score":null,"score_total":null,"note":"It adds interpretation instead of only listing rows: Rahul is framed as the strongest all-around customer, and the tool warns that Deepak and Karan's 'usual' payment method is not yet a stable preference because each has only one order.","artifact_count":2,"evidence_url":"https://aidemos.com/evidence/86d2a8b3-d9d0-4b8e-8e46-8bc17c6b5c6d"},{"id":"40517473-404e-484a-8697-bc2d5f2d8e13","criterion":"follow-up-context","criterion_name":"Follow-Up Context","rank_role":"context","verdict":"worked","score":null,"score_total":null,"note":"It carried the top 3 customers through both follow-ups and, on the payment-method question, correctly did not inherit the main query's paid/non-cancelled filter.","artifact_count":2,"evidence_url":"https://aidemos.com/evidence/40517473-404e-484a-8697-bc2d5f2d8e13"},{"id":"120ec9a3-5150-43ee-9111-4f936f2f833c","criterion":"sql-generation","criterion_name":"SQL Generation","rank_role":"decisive","verdict":"worked","score":null,"score_total":null,"note":"It generated CTE-based SQL that joins customers to paid, non-cancelled orders, aggregates order_count and total_spend, and ranks customers across both measures.","artifact_count":1,"evidence_url":"https://aidemos.com/evidence/120ec9a3-5150-43ee-9111-4f936f2f833c"}],"appears_in":[{"page_type":"ranking","slug":"ai-database-query-tools","title":"Best AI Tools to Query Live Databases Using Plain English","url":"https://aidemos.com/best/ai-database-query-tools","binding":"run"},{"page_type":"ranking","slug":"text-to-sql-tools","title":"Best AI Tools to Query Live Databases Using Plain English","url":"https://aidemos.com/best/text-to-sql-tools","binding":"study"},{"page_type":"use-case","slug":"query-live-databases","title":"Query Live Databases Using Plain English with AI","url":"https://aidemos.com/use-cases/query-live-databases","binding":"study"}],"same_scenario":[{"id":"6a130b11-3ffe-4dd1-b405-30c887af3d65","tool":"askyourdatabase","tool_name":"AskYourDatabase","verdict":"worked","score":null,"score_total":null,"note":"It presents the answer as clearly labeled ranking tables and customer-level payment summaries, with visual risk cues for unpaid or shipped orders."},{"id":"8631a190-2b78-4695-a457-2b0ac633578c","tool":"basedash","tool_name":"Basedash","verdict":"worked","score":null,"score_total":null,"note":"The output stays readable for non-technical users, using compact tables and short summaries with explicit customer names and amounts."},{"id":"cfe90f8a-a4cf-4c44-bafb-2e6f73ca7a40","tool":"definite","tool_name":"Definite","verdict":"worked","score":null,"score_total":null,"note":"It returns a ranked table with order counts, total spend, and average order value that is straightforward to read and scan."},{"id":"492b3c4c-2b5a-42db-80b7-7b8f2464e506","tool":"draxlr","tool_name":"Draxlr","verdict":"struggled","score":null,"score_total":null,"note":"All three best-customer result tables keep customer_id as the lead column, so the output stays UUID-heavy and hard to scan."},{"id":"ac7d4ce7-d376-4989-bb44-e8abdd293fbf","tool":"querio","tool_name":"Querio","verdict":"mixed","score":null,"score_total":null,"note":"The answer is usable, but it is less readable than it could be because the output centers customer UUIDs instead of human names."}]}