R-SET NOT_EQUAL
european_football_2 · mini_dev_postgresql from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json
What are the short name of team who played safe while creating chance of passing?
the hint the set supplies: played safe while creating chance of passing refers to chanceCreationPassingClass = 'Safe'; short name of team refers to team_short_name
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
read by hand, 2026-09-04: B harmless: one distinct row repeated; DISTINCT added by the prediction; a list under twice the answer with every row present
43 distinct names, 44 or 56 rows
a maintainer's reading of this question, out of classification.json, copied from plans/reports/prediction-mode-260904-real-predictions/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT DISTINCT t1.team_short_name FROM Team AS t1 INNER JOIN Team_Attributes AS t2 ON t1.team_api_id = t2.team_api_id WHERE t2.chanceCreationPassingClass = 'Safe'this statement states no ordering of its own
sha256:c6e437cd12ac3dd5536a9fcd2909e51b3acbd75968a2ace473c654f0d13f3d0e
SELECT Team.team_short_name
FROM Team
JOIN Team_Attributes ON Team.team_api_id = Team_Attributes.team_api_id
WHERE Team_Attributes.chanceCreationPassingClass = 'Safe'this statement states no ordering of its own
sha256:0034050fbfde37f8541945ee5ae477b5f0257b5873a6e094352ef010d0078cb1
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 | team_short_nametext |
|---|---|
| no rows |
from counterexample.json, 13 rows, up to 25 shown per side, 9 on this page
| side | times | team_short_nametext |
|---|---|---|
| second | 2 | ARS |
| second | 2 | BOL |
| second | 2 | GEN |
| second | 2 | WIS |
| second | 1 | CAG |
| second | 1 | LIV |
| second | 1 | NAC |
| second | 1 | REG |
| second | 1 | WHU |
set(second_rows) == set(gold_rows), float4/float8 cells as Python float as psycopg2 returns them, numeric as Decimal
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 PostgreSQL's as psycopg2 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, 43 rows, 25 on this page
| team_short_nametext |
|---|
| WHU |
| HUE |
| BET |
| ROD |
| NAC |
| BAR |
| SAM |
| WAA |
| EMP |
| HAA |
| UTR |
| UDI |
| NAP |
| ARL |
| BMU |
| WIS |
| ARK |
| COR |
| REG |
| STK |
| SPA |
| PSV |
| FRE |
| CAG |
| ZAG |
from counterexample.json, 56 rows, 25 on this page
| team_short_nametext |
|---|
| HAA |
| ARK |
| ARL |
| ARS |
| ARS |
| ARS |
| BAR |
| BMU |
| BOL |
| BOL |
| BOL |
| BRE |
| CAG |
| CAG |
| CAT |
| COR |
| DUF |
| EMP |
| COT |
| UTR |
| FRE |
| FRO |
| GEN |
| GEN |
| GEN |
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:c6e437cd12ac3dd5536a9fcd2909e51b3acbd75968a2ace473c654f0d13f3d0e",
"baseline_result": {
"columns": [
{
"name": "team_short_name",
"declared_type": "text"
}
],
"row_count": 43,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "WHU"
}
],
[
{
"type": "str",
"value": "HUE"
}
],
[
{
"type": "str",
"value": "BET"
}
],
[
{
"type": "str",
"value": "ROD"
}
],
[
{
"type": "str",
"value": "NAC"
}
],
[
{
"type": "str",
"value": "BAR"
}
],
[
{
"type": "str",
"value": "SAM"
}
],
[
{
"type": "str",
"value": "WAA"
}
],
[
{
"type": "str",
"value": "EMP"
}
],
[
{
"type": "str",
"value": "HAA"
}
]
],
"result_hash": "sha256:c6e437cd12ac3dd5536a9fcd2909e51b3acbd75968a2ace473c654f0d13f3d0e"
},
"planner_statistics": {
"team": {
"last_analyze": "2026-09-14 12:51:04.719781+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"team_attributes": {
"last_analyze": "2026-09-14 12:51:04.628002+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"team",
"team_attributes"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"laptimes": 400524,
"legalities": 427907,
"posthistory": 303155,
"trans": 1056320,
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:ee1cd443b1ab2b19b3a9ab6c8747e06c544e82f406dc24c9b00f21bd6c929d5f",
"result": {
"columns": [
{
"name": "team_short_name",
"declared_type": "text"
}
],
"row_count": 43,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "ARK"
}
],
[
{
"type": "str",
"value": "ARL"
}
],
[
{
"type": "str",
"value": "ARS"
}
],
[
{
"type": "str",
"value": "BAR"
}
],
[
{
"type": "str",
"value": "BET"
}
],
[
{
"type": "str",
"value": "BMU"
}
],
[
{
"type": "str",
"value": "BOL"
}
],
[
{
"type": "str",
"value": "BRE"
}
],
[
{
"type": "str",
"value": "CAG"
}
],
[
{
"type": "str",
"value": "CAT"
}
]
],
"result_hash": "sha256:ee1cd443b1ab2b19b3a9ab6c8747e06c544e82f406dc24c9b00f21bd6c929d5f"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}this statement returns the same whole row more than once and never says DISTINCT, so a statement answering the same question once per row disagrees on multiplicity alone
{
"heuristic": true,
"rows": 43,
"distinct_rows": 43,
"repeated_rows": 0,
"largest_repeat": 1,
"result_bounded": false,
"distinct_stated": true,
"set_operation": false,
"not_applicable": "the statement states DISTINCT, so it cannot repeat a row"
}SELECT DISTINCT t1.team_short_name FROM Team AS t1 INNER JOIN Team_Attributes AS t2 ON t1.team_api_id = t2.team_api_id WHERE t2.chanceCreationPassingClass = 'Safe'result_hash sha256:c6e437cd12ac3dd5536a9fcd2909e51b3acbd75968a2ace473c654f0d13f3d0e recomputed from this JSON: match
record_hash sha256:63c7809f7793261bf3ddbc0c9c11a92f466ae8b319e7f7f4e113048d2e917760 recomputed from this JSON: match
from evidence-gold.json, 43 rows
| team_short_nametext |
|---|
| WHU |
| HUE |
| BET |
| ROD |
| NAC |
| BAR |
| SAM |
| WAA |
| EMP |
| HAA |
| UTR |
| UDI |
| NAP |
| ARL |
| BMU |
| WIS |
| ARK |
| COR |
| REG |
| STK |
| SPA |
| PSV |
| FRE |
| CAG |
| ZAG |
| CAT |
| BRE |
| MCI |
| DUF |
| SIE |
| SAS |
| GEN |
| FRO |
| PAL |
| ARS |
| LOR |
| WII |
| LOK |
| BOL |
| LIV |
| GRF |
| COT |
| HER |
SELECT Team.team_short_name
FROM Team
JOIN Team_Attributes ON Team.team_api_id = Team_Attributes.team_api_id
WHERE Team_Attributes.chanceCreationPassingClass = 'Safe'result_hash sha256:0034050fbfde37f8541945ee5ae477b5f0257b5873a6e094352ef010d0078cb1 recomputed from this JSON: match
record_hash sha256:0db47f932f82d578d1e0e07bd42d2eaa91a9c3e36d85458e330959cbab84451d recomputed from this JSON: match
from evidence-second.json, 56 rows, 50 on this page
| team_short_nametext |
|---|
| HAA |
| ARK |
| ARL |
| ARS |
| ARS |
| ARS |
| BAR |
| BMU |
| BOL |
| BOL |
| BOL |
| BRE |
| CAG |
| CAG |
| CAT |
| COR |
| DUF |
| EMP |
| COT |
| UTR |
| FRE |
| FRO |
| GEN |
| GEN |
| GEN |
| GRF |
| HER |
| LIV |
| LIV |
| LOK |
| LOR |
| MCI |
| NAC |
| NAC |
| PAL |
| PSV |
| BET |
| HUE |
| REG |
| REG |
| SIE |
| ROD |
| SAM |
| SAS |
| SPA |
| NAP |
| STK |
| UDI |
| WAA |
| WHU |
The whole result is in evidence-second.json, beside this page.
re-run this statement read-only against PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird 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 PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET