R-ORD GOLD-ONLY ordering-over-numeric-text
formula_1 · 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)
For the driver who set the fastest lap speed, what is his nationality?
the hint the set supplies: the fastest lap speed refers to (MAX) fastestLapSpeed;
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
the ordering key is a text column of numbers, so 9.5 sorts above 10 and the fastest speed is not the one returned; reported upstream as mini_dev issue 24 and corrected in Mini-Dev's Hugging Face copy, still open in both copies of dev
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.nationality
FROM drivers AS T1
INNER JOIN results AS T2 ON T2.driverId = T1.driverId
ORDER BY T2.fastestLapSpeed DESC
LIMIT 1;sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8
from evidence-gold.json, 1 row
| nationalityTEXT |
|---|
| Italian |
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
from smells.json, 1 row
| Italian |
{
"heuristic": true,
"keys": [
{
"key": "T2.fastestLapSpeed",
"column": "results.fastestLapSpeed",
"declared_type": "TEXT",
"not_applicable": null,
"census": {
"rows": 23657,
"nulls": 18389,
"empty_strings": 0,
"non_numeric": 0,
"pattern": "^-?[0-9]+(\\.[0-9]+)?$"
},
"every_value_is_numeric": true,
"cast_sql": "SELECT T1.nationality FROM drivers AS T1 INNER JOIN results AS T2 ON T2.driverId = T1.driverId ORDER BY CAST(T2.fastestLapSpeed AS REAL) DESC LIMIT 1",
"verdict": "not_equal",
"gold_result": {
"columns": [
{
"name": "nationality",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Italian"
}
]
],
"result_hash": "sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8"
},
"cast_result": {
"columns": [
{
"name": "nationality",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Brazilian"
}
]
],
"result_hash": "sha256:70b7d91c0aabdb123b6a8c7cd552267250ddb185ca07709be266f86af22a3e10"
}
}
]
}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
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT T1.nationality, T2.fastestLapSpeed AS attestql_ordering_key_0 FROM drivers AS T1 INNER JOIN results AS T2 ON T2.driverId = T1.driverId ORDER BY T2.fastestLapSpeed DESC",
"unbounded_rows": 23657,
"projected_columns": [
"nationality"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "T2.fastestLapSpeed",
"direction": "desc",
"nulls": "last",
"nulls_first_in_effect": false,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"case": null
}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:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8",
"baseline_result": {
"columns": [
{
"name": "nationality",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Italian"
}
]
],
"result_hash": "sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"drivers",
"results"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"lapTimes": 420369
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8",
"result": {
"columns": [
{
"name": "nationality",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Italian"
}
]
],
"result_hash": "sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T1.nationality
FROM drivers AS T1
INNER JOIN results AS T2 ON T2.driverId = T1.driverId
ORDER BY T2.fastestLapSpeed DESC
LIMIT 1;result_hash sha256:428c7015f613b8f3fdcd341c91acf189665dd7f82ed4d65adc02646898f4f5e8 recomputed from this JSON: match
record_hash sha256:26491e7540079d2978285de28de2173341da32e2637ee738c625cfb7bfe4e6b3 recomputed from this JSON: match
from evidence-gold.json, 1 row
| nationalityTEXT |
|---|
| Italian |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/formula_1/formula_1.sqlite | size=22360064 under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD