R-ORD GOLD-ONLY arbitrary-cut
superhero · dev_20251106-00000-of-00001 from https://huggingface.co/datasets/birdsql/bird_sql_dev_20251106/resolve/3c11fb193e5439b338e23677fa0aae11e8b85db9/data/dev_20251106-00000-of-00001.json (commit 3c11fb19, downloaded 2026-09-07)
What is the hero's full name with the highest attribute in strength?
the hint the set supplies: highest attribute in strength refers to MAX(attribute_value) WHERE attribute_name = 'strength';
This question was audited without a prediction beside it, so there is nothing to compare the gold with. The probes below read the gold alone.
read by hand, 2026-09-07: wrong the gold does not answer its question on this data
63 rows tie on the largest strength value, 36 of them naming a different hero
a maintainer's reading of this question, out of classification.json, copied from plans/reports/bird-dev-sqlite-260907/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT T1.full_name FROM superhero AS T1 INNER JOIN hero_attribute AS T2 ON T1.id = T2.hero_id INNER JOIN attribute AS T3 ON T2.attribute_id = T3.id WHERE T3.attribute_name = 'Strength' ORDER BY T2.attribute_value DESC LIMIT 1sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf
from evidence-gold.json, 1 row
| full_nameTEXT |
|---|
| Richard Milhouse Jones |
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
no ORDER BY key resolves to a text column
{
"heuristic": true,
"reason": "no ORDER BY key resolves to a text column",
"keys": [
{
"key": "T2.attribute_value",
"column": "hero_attribute.attribute_value",
"declared_type": "INTEGER",
"not_applicable": "the column is not declared as text"
}
]
}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
from smells.json, 10 rows
| Richard Milhouse Jones | 100 |
| Abraxas | 100 |
| - | 100 |
| - | 100 |
| En Sabah Nur | 100 |
| - | 100 |
| - | 100 |
| - | 100 |
| Erik Stephan Josten | 100 |
| Benjamin Kirby Tennyson | 100 |
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT T1.full_name, T2.attribute_value AS attestql_ordering_key_0 FROM superhero AS T1 INNER JOIN hero_attribute AS T2 ON T1.id = T2.hero_id INNER JOIN attribute AS T3 ON T2.attribute_id = T3.id WHERE T3.attribute_name = 'Strength' ORDER BY T2.attribute_value DESC",
"unbounded_rows": 623,
"projected_columns": [
"full_name"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "T2.attribute_value",
"direction": "desc",
"nulls": "last",
"nulls_first_in_effect": false,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"tied_at_the_cut": {
"positions": [
0,
1,
2,
3,
4,
5,
6,
7,
8,
9
],
"tied_rows": 63,
"distinct_projected_answers": 36,
"rows": [
[
{
"type": "str",
"value": "Richard Milhouse Jones"
}
],
[
{
"type": "str",
"value": "Abraxas"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "En Sabah Nur"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "Erik Stephan Josten"
}
],
[
{
"type": "str",
"value": "Benjamin Kirby Tennyson"
}
]
]
},
"case": "tie-at-the-cut"
}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-ORD",
"baseline_result_hash": "sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf",
"baseline_result": {
"columns": [
{
"name": "full_name",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Richard Milhouse Jones"
}
]
],
"result_hash": "sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"superhero",
"hero_attribute",
"attribute"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf",
"result": {
"columns": [
{
"name": "full_name",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Richard Milhouse Jones"
}
]
],
"result_hash": "sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T1.full_name FROM superhero AS T1 INNER JOIN hero_attribute AS T2 ON T1.id = T2.hero_id INNER JOIN attribute AS T3 ON T2.attribute_id = T3.id WHERE T3.attribute_name = 'Strength' ORDER BY T2.attribute_value DESC LIMIT 1result_hash sha256:d66638124bfc89c4fdab1459171f13b89d00666fe33abb4f7db586b4d9dc31bf recomputed from this JSON: match
record_hash sha256:2e5005f5809e968538e1c1cceb173155ec87734368465385a3177141fb6a322b recomputed from this JSON: match
from evidence-gold.json, 1 row
| full_nameTEXT |
|---|
| Richard Milhouse Jones |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/superhero/superhero.sqlite | size=237568 under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD