R-SET NOT_EQUAL
card_games · mini_dev_sqlite from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_sqlite.json
What's the Italian name of the set of cards with "Ancestor's Chosen" is in?
the hint the set supplies: Italian is a language which refers to language = 'Italian'; with "Ancestor's Chosen" in the card set refers to name = 'Ancestor''s Chosen'
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
SELECT translation FROM set_translations WHERE setCode IN ( SELECT setCode FROM cards WHERE name = 'Ancestor''s Chosen' ) AND language = 'Italian'this statement states no ordering of its own
sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6
SELECT st.translation
FROM cards c
JOIN sets s ON c.setCode = s.code
JOIN set_translations st ON s.code = st.setCode
WHERE c.name = 'Ancestor''s Chosen' AND st.language = 'Italian'this statement states no ordering of its own
sha256:087b4d996d9a38a72e96a86998335f2bf86d9139c3698952dbea5bf8e013ec87
The marked tokens are where the two texts differ. Two statements that differ everywhere can return the same rows, and two that differ in one token can return other rows; the verdict above is read off the results.
from counterexample.json, 0 rows, up to 25 shown per side
| side | translationTEXT |
|---|---|
| no rows |
from counterexample.json, 1 row, up to 25 shown per side
| side | translationTEXT |
|---|---|
| second | Set Base Decima Edizione |
set(second_rows) == set(gold_rows), REAL cells as Python float as sqlite3 returns them, so Python equality holds 1 == 1.0 == True as the benchmark's own scorer does
https://github.com/bird-bench/mini_dev/blob/main/evaluation/evaluation_ex.py
result_eq: equal row counts and equal column counts, each row unordered as a quick rejection, then the two equal as a list when the gold text holds ORDER BY and as a multiset otherwise, under some permutation of the columns; DISTINCT is not stripped and re-executed, and the cells are SQLite's as sqlite3 returns them
ruiqi-zhong/test-suite-sql-eval, exec_eval.py, result_eq, at commit 48cb78ec: https://github.com/ruiqi-zhong/test-suite-sql-eval/blob/48cb78ecf7f610620206283846c76751b18a1326/exec_eval.py
The class states what makes these two results unequal under this rule, read off the two results and nothing else. It does not state which of the two statements is wrong.
from counterexample.json, 2 rows
| translationTEXT |
|---|
| Set Base Decima Edizione |
| Sentenza |
from counterexample.json, 3 rows
| translationTEXT |
|---|
| Set Base Decima Edizione |
| Set Base Decima Edizione |
| Sentenza |
A smell is a mechanical reason to read this gold statement again. It is a heuristic: it does not state that the statement is wrong, and a maintainer decides.
this statement orders by a text column holding only numbers, and ordering it as a number gives a different answer, so the gold may be sorting 9.5 above 10
the statement states no top level ORDER BY
{
"heuristic": true,
"reason": "the statement states no top level ORDER BY"
}this statement cuts its result at a LIMIT that does not decide which rows come back, so a different but equally correct statement can return other rows and score zero
the statement states no LIMIT
{
"heuristic": true,
"reason": "the statement states no LIMIT"
}rerun over the same rows in another physical order this statement gives another answer, so its result depends on how the rows are stored and not only on the data
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6",
"baseline_result": {
"columns": [
{
"name": "translation",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Set Base Decima Edizione"
}
],
[
{
"type": "str",
"value": "Sentenza"
}
]
],
"result_hash": "sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"set_translations",
"cards"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"legalities": 427907
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6",
"result": {
"columns": [
{
"name": "translation",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Set Base Decima Edizione"
}
],
[
{
"type": "str",
"value": "Sentenza"
}
]
],
"result_hash": "sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT translation FROM set_translations WHERE setCode IN ( SELECT setCode FROM cards WHERE name = 'Ancestor''s Chosen' ) AND language = 'Italian'result_hash sha256:2fa72388e061cfd367573c101feccfb827cf9e534314f1de4e132764d498cef6 recomputed from this JSON: match
record_hash sha256:f4c1d5032a4bcaf1e761f95e352116963f0a0cdd388385f516e096d1f1648af4 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| translationTEXT |
|---|
| Set Base Decima Edizione |
| Sentenza |
SELECT st.translation
FROM cards c
JOIN sets s ON c.setCode = s.code
JOIN set_translations st ON s.code = st.setCode
WHERE c.name = 'Ancestor''s Chosen' AND st.language = 'Italian'result_hash sha256:087b4d996d9a38a72e96a86998335f2bf86d9139c3698952dbea5bf8e013ec87 recomputed from this JSON: match
record_hash sha256:aded0bffbb5ff7f17802d66d171f23846de152a4a0505bff6fd97adfc9dc0304 recomputed from this JSON: match
from evidence-second.json, 3 rows
| translationTEXT |
|---|
| Set Base Decima Edizione |
| Set Base Decima Edizione |
| Sentenza |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/dev_databases/card_games/card_games.sqlite | size=261820416 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/dev_databases/card_games/card_games.sqlite | size=261820416 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET