q255 NOT_EQUAL

The question

What proportion of single bonds are carcinogenic? Please provide your answer as a percentage with five decimal places.

the hint the set supplies: single bond refers to bond_type = '-'; label = '+' mean molecules are carcinogenic; proportion = DIVIDE(SUM(label = '+') * 100, COUNT(bond_id)) where bond_type = '-'

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: A a wrong answer the benchmark credited: another table or projection; a scalar repeated per row of an unrelated table; a list at least twice the answer's length where the question asks for the things, not the rows

a percentage computed by scalar subqueries, then selected once per row of molecule: 343 identical 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 two statements name their result columns differently. A projection is compared by position and declared type, so these names did not decide the verdict. They are part of the canonical rendering each result is hashed under, so the two result hashes differ with them.

gold: percentage
prediction: proportion_carcinogenic_single_bonds

The statements

gold

SELECT ROUND(CAST((CAST(COUNT(CASE WHEN T2.label = '+' THEN T1.bond_id ELSE NULL END) AS REAL) * 100 / NULLIF(COUNT(T1.bond_id), 0)) AS NUMERIC), 5) AS percentage FROM bond AS T1 INNER JOIN molecule AS T2 ON T1.molecule_id = T2.molecule_id WHERE T1.bond_type = '-'

this statement states no ordering of its own

sha256:596884a4fc335169b38628cf6e0f541f7138e22421a7c1dce229a9cec178c7ee

second

SELECT ROUND(
    (
        SELECT COUNT(*) 
        FROM molecule m 
        JOIN bond b ON m.molecule_id = b.molecule_id 
        WHERE b.bond_type = '-' AND m.label = '+'
    )::decimal / 
    (
        SELECT COUNT(*) 
        FROM bond 
        WHERE bond_type = '-'
    ) * 100, 5
) AS proportion_carcinogenic_single_bonds
FROM molecule

this statement states no ordering of its own

sha256:d0cda7badd938ebf5aebb9a300332ab3dde8adf5226fe6e4bda513cb46771f15

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

in the prediction, not in gold, 342 rows

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

side	times	proportion_carcinogenic_single_bondsnumeric
second	342	39.75203

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: 343
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: 343
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 343. 1 rows occur in both results at least once.

gold_types: ["numeric"]
second_types: ["numeric"]
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

percentagenumeric
39.75203

second, 343 rows

from counterexample.json, 343 rows, 25 on this page

proportion_carcinogenic_single_bondsnumeric
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203

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:596884a4fc335169b38628cf6e0f541f7138e22421a7c1dce229a9cec178c7ee",
  "baseline_result": {
    "columns": [
      {
        "name": "percentage",
        "declared_type": "numeric"
      }
    ],
    "row_count": 1,
    "truncated": false,
    "rows_shown": 1,
    "rows": [
      [
        {
          "type": "dec",
          "value": "39.75203"
        }
      ]
    ],
    "result_hash": "sha256:596884a4fc335169b38628cf6e0f541f7138e22421a7c1dce229a9cec178c7ee"
  },
  "planner_statistics": {
    "bond": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:12.802916+00",
      "n_mod_since_analyze": 0
    },
    "molecule": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:30.558409+00",
      "n_mod_since_analyze": 0
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "bond",
      "molecule"
    ],
    "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:596884a4fc335169b38628cf6e0f541f7138e22421a7c1dce229a9cec178c7ee",
    "result": {
      "columns": [
        {
          "name": "percentage",
          "declared_type": "numeric"
        }
      ],
      "row_count": 1,
      "truncated": false,
      "rows_shown": 1,
      "rows": [
        [
          {
            "type": "dec",
            "value": "39.75203"
          }
        ]
      ],
      "result_hash": "sha256:596884a4fc335169b38628cf6e0f541f7138e22421a7c1dce229a9cec178c7ee"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT ROUND(CAST((CAST(COUNT(CASE WHEN T2.label = '+' THEN T1.bond_id ELSE NULL END) AS REAL) * 100 / NULLIF(COUNT(T1.bond_id), 0)) AS NUMERIC), 5) AS percentage FROM bond AS T1 INNER JOIN molecule AS T2 ON T1.molecule_id = T2.molecule_id WHERE T1.bond_type = '-'

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

record_hash sha256:d12b65d24d64dd9e79dcd1982d1708be19f481e258fe1d916defe610e85138d1 recomputed from this JSON: match

the result this record holds, 1 row

from evidence-gold.json, 1 row

percentagenumeric
39.75203

what ran, and where

run: audit-eacac37d-7cc4-4d44-9121-67cecbf29b75
executed at: 2026-09-08T05:22:21.501574+00:00
data as of: 2026-09-08T05:21:47.344133+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:ba1313ccad7346690accb8f37e8267cdf5724a0f7caf06cb34a49c00fc3980db
source file sha256: sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.bond: 9156
rows in public.molecule: 343

second: evidence-second.json

SELECT ROUND(
    (
        SELECT COUNT(*) 
        FROM molecule m 
        JOIN bond b ON m.molecule_id = b.molecule_id 
        WHERE b.bond_type = '-' AND m.label = '+'
    )::decimal / 
    (
        SELECT COUNT(*) 
        FROM bond 
        WHERE bond_type = '-'
    ) * 100, 5
) AS proportion_carcinogenic_single_bonds
FROM molecule

statement read from: data/preds-pg/predict_mini_dev_gpt-4-32k_postgresql.json
digest: sha256:0fba1bfbeb487d641c8ae1e8bb01f762b2d29ddfb7c14dbd94e832f53cc10270
origin: https://raw.githubusercontent.com/bird-bench/mini_dev/b3d4bcbbae9a96934ad812551eb400c7a3b23c12/llm/exp_result/sql_output_kg/predict_mini_dev_gpt-4-32k_postgresql.json, 2024-06-19

result_hash sha256:d0cda7badd938ebf5aebb9a300332ab3dde8adf5226fe6e4bda513cb46771f15 recomputed from this JSON: match

record_hash sha256:8971350150cf4d387ac31774674ec7f060c832448fe9dece1ba3e81db9dd3ac1 recomputed from this JSON: match

the result this record holds, 343 rows

from evidence-second.json, 343 rows

proportion_carcinogenic_single_bondsnumeric
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203
39.75203

what ran, and where

run: audit-eacac37d-7cc4-4d44-9121-67cecbf29b75
executed at: 2026-09-08T05:22:21.506428+00:00
data as of: 2026-09-08T05:21:47.344133+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: 343 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:ba1313ccad7346690accb8f37e8267cdf5724a0f7caf06cb34a49c00fc3980db
source file sha256: sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.bond: 9156
rows in public.molecule: 343

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-eacac37d-7cc4-4d44-9121-67cecbf29b75
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, 342 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