q978

R-SET NOT_EQUAL

formula_1 · 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

The question

How many times the circuits were held in Austria? Please give their location and coordinates.

the hint the set supplies: location coordinates refers to (lat,lng); Austria refers to country = 'Austria';

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

2 distinct rows, 3 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.

The statements

gold

SELECT DISTINCT location, lat, lng FROM circuits WHERE country = 'Austria'

this statement states no ordering of its own

sha256:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351

second

SELECT location, lat, lng FROM circuits WHERE country = 'Austria'

this statement states no ordering of its own

sha256:82bb07e2b9e169e0063a7c05412a47e6889ebda0ae511e610ffda490800eb5c2

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.

The rows they differ in

in gold, not in the prediction, 0 rows

from counterexample.json, 0 rows, up to 25 shown per side

side locationtext latfloat4 lngfloat4
no rows

in the prediction, not in gold, 1 row

from counterexample.json, 1 row, up to 25 shown per side

side locationtext latfloat4 lngfloat4
second Spielburg 47.2197 14.7647

What the benchmark would have said

BIRD's own check: 1

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

gold_rows
2
second_rows
3
gold_distinct_rows
2
second_distinct_rows
2

the test-suite check: 0

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

order_matters
false
gold_rows
2
second_rows
3
gold_columns
3
second_columns
3

the class: multiplicity

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.

how many rows each result holds, and how many rows both hold, from evidence-gold.json and evidence-second.json2 gold3 prediction2 rows both results hold
The gold returned 2 rows and the prediction 3. 2 rows occur in both results at least once.
gold_types
["text", "float4", "float4"]
second_types
["text", "float4", "float4"]
multiset_equal
false
set_equal
true
order_equal
false
shorter_result_is_a_prefix
true

The results

gold, 2 rows

from counterexample.json, 2 rows

locationtext latfloat4 lngfloat4
Spielburg 47.2197 14.7647
Styria 47.2039 14.7478
second, 3 rows

from counterexample.json, 3 rows

locationtext latfloat4 lngfloat4
Spielburg 47.2197 14.7647
Styria 47.2039 14.7478
Spielburg 47.2197 14.7647

The probes

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.

ordering-over-numeric-text not applicable

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

what it measured 
{
  "heuristic": true,
  "reason": "the statement states no top level ORDER BY"
}

arbitrary-cut not applicable

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

what it measured 
{
  "heuristic": true,
  "reason": "the statement states no LIMIT"
}

not-a-function-of-the-data quiet

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

what it measured 
{
  "heuristic": true,
  "rule": "R-SET",
  "baseline_result_hash": "sha256:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351",
  "baseline_result": {
    "columns": [
      {
        "name": "location",
        "declared_type": "text"
      },
      {
        "name": "lat",
        "declared_type": "float4"
      },
      {
        "name": "lng",
        "declared_type": "float4"
      }
    ],
    "row_count": 2,
    "truncated": false,
    "rows_shown": 2,
    "rows": [
      [
        {
          "type": "str",
          "value": "Spielburg"
        },
        {
          "type": "dec",
          "value": "47.2197"
        },
        {
          "type": "dec",
          "value": "14.7647"
        }
      ],
      [
        {
          "type": "str",
          "value": "Styria"
        },
        {
          "type": "dec",
          "value": "47.2039"
        },
        {
          "type": "dec",
          "value": "14.7478"
        }
      ]
    ],
    "result_hash": "sha256:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351"
  },
  "planner_statistics": {
    "circuits": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:12.766783+00",
      "n_mod_since_analyze": 0
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "circuits"
    ],
    "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:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351",
    "result": {
      "columns": [
        {
          "name": "location",
          "declared_type": "text"
        },
        {
          "name": "lat",
          "declared_type": "float4"
        },
        {
          "name": "lng",
          "declared_type": "float4"
        }
      ],
      "row_count": 2,
      "truncated": false,
      "rows_shown": 2,
      "rows": [
        [
          {
            "type": "str",
            "value": "Spielburg"
          },
          {
            "type": "dec",
            "value": "47.2197"
          },
          {
            "type": "dec",
            "value": "14.7647"
          }
        ],
        [
          {
            "type": "str",
            "value": "Styria"
          },
          {
            "type": "dec",
            "value": "47.2039"
          },
          {
            "type": "dec",
            "value": "14.7478"
          }
        ]
      ],
      "result_hash": "sha256:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT DISTINCT location, lat, lng FROM circuits WHERE country = 'Austria'
statement read from
data/questions/mini_dev_postgresql.json
digest
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
origin
https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json, 2024-06-19

result_hash sha256:05076efc0115e818e17e81114745f4c03c3892adf67f5af7870bac75cdd3f351 recomputed from this JSON: match

record_hash sha256:f135f1024c34feab5a10cf931b662169d12e82adb4d0ef94f726a215f9cadf70 recomputed from this JSON: match

the result this record holds, 2 rows

from evidence-gold.json, 2 rows

locationtext latfloat4 lngfloat4
Spielburg 47.2197 14.7647
Styria 47.2039 14.7478
what ran, and where
run
audit-7912134a-3f9b-4113-a6b6-ebaf8b6a2bc0
executed at
2026-09-08T05:22:54.930965+00:00
data as of
2026-09-08T05:22:38.535771+00:00
backend at checkout
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
backend that answered
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
database role
auditor
replay rule
R-SET
question set version
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
validator
audit:libpg_query-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
120000 ms
rows
2 rows
the session it ran under
engine
postgresql
time_zone
Etc/UTC
date_style
ISO, MDY
interval_style
postgres
extra_float_digits
1
database_collation
en_US.utf8
work_mem
4096
hash_mem_multiplier
2

recorded beside them

statement_timeout
0
search_path
"$user", public
server_version
16.15 (Debian 16.15-1.pgdg13+2)
server_version_num
160015
transaction_read_only
on
max_parallel_workers_per_gather
2
server_encoding
UTF8
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/2
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:dba8a9a92336f39850ac0e5248f8ef476f2bc8ca791dd5ec46b668424980980f
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.circuits
72

second: evidence-second.json

SELECT location, lat, lng FROM circuits WHERE country = 'Austria'
statement read from
data/preds-pg/predict_mini_dev_gpt-4-turbo_postgresql.json
digest
sha256:428fd115a67a76d6312ea205aab64764b5a09444587588eda442a94cfee65211
origin
https://raw.githubusercontent.com/bird-bench/mini_dev/b3d4bcbbae9a96934ad812551eb400c7a3b23c12/llm/exp_result/sql_output_kg/predict_mini_dev_gpt-4-turbo_postgresql.json, 2024-06-19

result_hash sha256:82bb07e2b9e169e0063a7c05412a47e6889ebda0ae511e610ffda490800eb5c2 recomputed from this JSON: match

record_hash sha256:bdc187631e739fb92e046e571c54f8a46a48b0387f7a3d32d528fe333719ebe8 recomputed from this JSON: match

the result this record holds, 3 rows

from evidence-second.json, 3 rows

locationtext latfloat4 lngfloat4
Spielburg 47.2197 14.7647
Styria 47.2039 14.7478
Spielburg 47.2197 14.7647
what ran, and where
run
audit-7912134a-3f9b-4113-a6b6-ebaf8b6a2bc0
executed at
2026-09-08T05:22:54.933855+00:00
data as of
2026-09-08T05:22:38.535771+00:00
backend at checkout
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
backend that answered
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
database role
auditor
replay rule
R-SET
question set version
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
validator
audit:libpg_query-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
120000 ms
rows
3 rows
the session it ran under
engine
postgresql
time_zone
Etc/UTC
date_style
ISO, MDY
interval_style
postgres
extra_float_digits
1
database_collation
en_US.utf8
work_mem
4096
hash_mem_multiplier
2

recorded beside them

statement_timeout
0
search_path
"$user", public
server_version
16.15 (Debian 16.15-1.pgdg13+2)
server_version_num
160015
transaction_read_only
on
max_parallel_workers_per_gather
2
server_encoding
UTF8
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/2
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:dba8a9a92336f39850ac0e5248f8ef476f2bc8ca791dd5ec46b668424980980f
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.circuits
72

Running these again

gold

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

second

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

This question's run

run
audit-7912134a-3f9b-4113-a6b6-ebaf8b6a2bc0
server
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
question set
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
replay rule
R-SET

the run this question belongs to

The JSON this page was rendered from