q358 NOT_EQUAL

The question

What is the border color of card "Ancestor's Chosen"?

the hint the set supplies: name of card = '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.

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

one distinct row (black) repeated, once per printing

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 borderColor FROM cards WHERE name = 'Ancestor''s Chosen'

this statement states no ordering of its own

sha256:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7

second

SELECT cards.bordercolor
FROM cards
WHERE cards.name = 'Ancestor''s Chosen'

this statement states no ordering of its own

sha256:d5482d6d0006c6f410431e40bb4868c85f28caee0c8aa6d1ae5a967522ec81d6

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	bordercolortext
no rows

in the prediction, not in gold, 3 rows

from counterexample.json, 3 rows, up to 25 shown per side, 1 on this page

side	times	bordercolortext
second	3	black

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: 1
second_rows: 4
gold_distinct_rows: 1
second_distinct_rows: 1

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: 1
second_rows: 4
gold_columns: 1
second_columns: 1

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.

The gold returned 1 rows and the prediction 4. 1 rows occur in both results at least once.

gold_types: ["text"]
second_types: ["text"]
multiset_equal: false
set_equal: true
order_equal: false
shorter_result_is_a_prefix: true

The results

gold, 1 row

from counterexample.json, 1 row

bordercolortext
black

second, 4 rows

from counterexample.json, 4 rows

bordercolortext
black
black
black
black

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:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7",
  "baseline_result": {
    "columns": [
      {
        "name": "bordercolor",
        "declared_type": "text"
      }
    ],
    "row_count": 1,
    "truncated": false,
    "rows_shown": 1,
    "rows": [
      [
        {
          "type": "str",
          "value": "black"
        }
      ]
    ],
    "result_hash": "sha256:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7"
  },
  "planner_statistics": {
    "cards": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:16.814042+00",
      "n_mod_since_analyze": 0
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "cards"
    ],
    "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:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7",
    "result": {
      "columns": [
        {
          "name": "bordercolor",
          "declared_type": "text"
        }
      ],
      "row_count": 1,
      "truncated": false,
      "rows_shown": 1,
      "rows": [
        [
          {
            "type": "str",
            "value": "black"
          }
        ]
      ],
      "result_hash": "sha256:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT DISTINCT borderColor FROM cards WHERE name = 'Ancestor''s Chosen'

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:d9f3da20d306bd421e73114c5e7176f4611d2c45574ef54f5bfeff02e6cfa6f7 recomputed from this JSON: match

record_hash sha256:8f789699acd56d241786809953b0d5a02211e0bbb8a32ddc33180ab9615c4040 recomputed from this JSON: match

the result this record holds, 1 row

from evidence-gold.json, 1 row

bordercolortext
black

what ran, and where

run: audit-a7e6b760-f8ad-479a-b956-9cd88ea91e18
executed at: 2026-09-08T05:21:32.534417+00:00
data as of: 2026-09-08T05:21:06.155844+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: 1 row

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:561b171d86e9868bbc46192590383dbedd283a399e48674c300eec7f1cb5f477
source file sha256: sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.cards: 56822

second: evidence-second.json

SELECT cards.bordercolor
FROM cards
WHERE cards.name = 'Ancestor''s Chosen'

statement read from: data/preds-pg/predict_mini_dev_gpt-35-turbo_postgresql.json
digest: sha256:fa363fe3c3fc45d97cb47e6ec15133b291acccd750e5136b6e7b4d1c8d13a4be
origin: https://raw.githubusercontent.com/bird-bench/mini_dev/b3d4bcbbae9a96934ad812551eb400c7a3b23c12/llm/exp_result/sql_output_kg/predict_mini_dev_gpt-35-turbo_postgresql.json, 2024-06-19

result_hash sha256:d5482d6d0006c6f410431e40bb4868c85f28caee0c8aa6d1ae5a967522ec81d6 recomputed from this JSON: match

record_hash sha256:0f8a10acbc7256a9776b4e92bdbd03f3081b5debdae347a5503e1ed51cd16717 recomputed from this JSON: match

the result this record holds, 4 rows

from evidence-second.json, 4 rows

bordercolortext
black
black
black
black

what ran, and where

run: audit-a7e6b760-f8ad-479a-b956-9cd88ea91e18
executed at: 2026-09-08T05:21:32.555021+00:00
data as of: 2026-09-08T05:21:06.155844+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: 4 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:561b171d86e9868bbc46192590383dbedd283a399e48674c300eec7f1cb5f477
source file sha256: sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.cards: 56822

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

This question's run

run: audit-a7e6b760-f8ad-479a-b956-9cd88ea91e18
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

counterexample.json attestql/audit/counterexample/2
evidence-gold.json the gold's evidence record
evidence-second.json the prediction's evidence record
smells.json attestql/audit/smells/2

The question

The statements

◀ gold

▶ second

The rows they differ in

in gold, not in the prediction, 0 rows

in the prediction, not in gold, 3 rows

What the benchmark would have said

BIRD's own check: 1

the test-suite check: 0

the class: multiplicity

The results

The probes

ordering-over-numeric-text not applicable

arbitrary-cut not applicable

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

The evidence records

gold: evidence-gold.json

recorded beside them

second: evidence-second.json

recorded beside them

Running these again

gold

second

This question's run

The JSON this page was rendered from

gold

second