q1290

R-ORD GOLD-ONLY arbitrary-cut

thrombosis_prediction · 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)

The question

What is the examination date of the patient whose albumin is the highest in the normal range?

the hint the set supplies: examination date refers to Date; albumin is the highest in the normal range refers to MAX(ALB > 3.5 and ALB < 5.5);

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

four laboratory rows share the largest albumin value inside the stated range and carry four different dates

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.

The statements

gold

SELECT Date FROM Laboratory WHERE ALB > 3.5 AND ALB < 5.5 ORDER BY ALB DESC LIMIT 1
ALB
descending

sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa

The results

gold, 1 row

from evidence-gold.json, 1 row

DateTEXT
1981-06-01

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

no ORDER BY key resolves to a text column

what it measured 
{
  "heuristic": true,
  "reason": "no ORDER BY key resolves to a text column",
  "keys": [
    {
      "key": "ALB",
      "column": "Laboratory.ALB",
      "declared_type": "REAL",
      "not_applicable": "the column is not declared as text"
    }
  ]
}

arbitrary-cut fired

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, 4 rows

1981-06-01 5.4
1984-08-06 5.4
1985-01-12 5.4
1985-02-15 5.4
what it measured 
{
  "heuristic": true,
  "cut": 1,
  "offset": 0,
  "distinct_kept": false,
  "unbounded_sql": "SELECT Date, ALB AS attestql_ordering_key_0 FROM Laboratory WHERE ALB > 3.5 AND ALB < 5.5 ORDER BY ALB DESC",
  "unbounded_rows": 10021,
  "projected_columns": [
    "Date"
  ],
  "ordering_key_columns": [
    "attestql_ordering_key_0"
  ],
  "ordering_keys": [
    {
      "key": "ALB",
      "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
    ],
    "tied_rows": 4,
    "distinct_projected_answers": 4,
    "rows": [
      [
        {
          "type": "str",
          "value": "1981-06-01"
        }
      ],
      [
        {
          "type": "str",
          "value": "1984-08-06"
        }
      ],
      [
        {
          "type": "str",
          "value": "1985-01-12"
        }
      ],
      [
        {
          "type": "str",
          "value": "1985-02-15"
        }
      ]
    ]
  },
  "case": "tie-at-the-cut"
}

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-ORD",
  "baseline_result_hash": "sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa",
  "baseline_result": {
    "columns": [
      {
        "name": "Date",
        "declared_type": "TEXT"
      }
    ],
    "row_count": 1,
    "truncated": false,
    "rows_shown": 1,
    "rows": [
      [
        {
          "type": "str",
          "value": "1981-06-01"
        }
      ]
    ],
    "result_hash": "sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa"
  },
  "planner_statistics": {},
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "Laboratory"
    ],
    "tables_not_shuffled": [],
    "tables_skipped_for_size": {},
    "tables_not_reached_by_a_copy": {}
  },
  "shuffled_copies": {
    "run": true,
    "verdict": "equal",
    "differs": false,
    "result_hash": "sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa",
    "result": {
      "columns": [
        {
          "name": "Date",
          "declared_type": "TEXT"
        }
      ],
      "row_count": 1,
      "truncated": false,
      "rows_shown": 1,
      "rows": [
        [
          {
            "type": "str",
            "value": "1981-06-01"
          }
        ]
      ],
      "result_hash": "sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT Date FROM Laboratory WHERE ALB > 3.5 AND ALB < 5.5 ORDER BY ALB DESC LIMIT 1
statement read from
data/questions/dev_20251106-00000-of-00001.json
digest
sha256:ffd8018378ddb1a8794753e0a31cfc81862ff7318a5184c22f3dc4ce03a03feb
origin
https://huggingface.co/datasets/birdsql/bird_sql_dev_20251106/resolve/3c11fb193e5439b338e23677fa0aae11e8b85db9/data/dev_20251106-00000-of-00001.json (commit 3c11fb19, downloaded 2026-09-07), 2026-01-18T08:51:02Z

result_hash sha256:1aea2d470b55830060d5fc1378d76f94e525a5e670eb325b0146218a38a177aa recomputed from this JSON: match

record_hash sha256:4d78aa8422dff32151803adf432138524f8ad2c88da2e2d379f85d930175a7c7 recomputed from this JSON: match

the result this record holds, 1 row

from evidence-gold.json, 1 row

DateTEXT
1981-06-01
what ran, and where
run
audit-81b79d57-0fa4-459a-9c7a-72e804752908
executed at
2026-09-08T04:58:55.834861+00:00
data as of
2026-09-08T04:58:55.059074+00:00
backend at checkout
SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/thrombosis_prediction/thrombosis_prediction.sqlite | size=7327744
backend that answered
SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/thrombosis_prediction/thrombosis_prediction.sqlite | size=7327744
database role
file
replay rule
R-ORD
question set version
sha256:ffd8018378ddb1a8794753e0a31cfc81862ff7318a5184c22f3dc4ce03a03feb
validator
audit:sqlglot-sqlite-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
30000 ms
rows
1 row
the session it ran under
engine
sqlite
time_zone
not stated by this engine
date_style
not stated by this engine
interval_style
not stated by this engine
extra_float_digits
not stated by this engine
database_collation
not stated by this engine
work_mem
not stated by this engine
hash_mem_multiplier
not stated by this engine

recorded beside them

sqlite_version
3.53.4
encoding
UTF-8
reverse_unordered_selects
0
query_only
1
journal_mode
delete
data_version
1
compile_options
ATOMIC_INTRINSICS=1,COMPILER=clang-21.0.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,DIRECT_OVERFLOW_READ,ENABLE_API_ARMOR,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_MATH_FUNCTIONS,ENABLE_MEMORY_MANAGEMENT,ENABLE_PERCENTILE,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_STAT4,ENABLE_UNLOCK_NOTIFY,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=1000,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=0xfffffffe,MAX_PAGE_SIZE=65536,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1,USE_URI
collation_list
RTRIM,NOCASE,BINARY
case_sensitive_like
0
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:804de22e3bc16326861badd2747684e3cbf8df7c399b3918952fec2781077eba
source file sha256
sha256:e7e16d74b4731b4b8d33fdbe8c29cd5622620788ce8d1f335631f65fc7cf1db9
rows in main.Laboratory
13908

Running these again

gold

re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/thrombosis_prediction/thrombosis_prediction.sqlite | size=7327744 under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD

This question's run

run
audit-81b79d57-0fa4-459a-9c7a-72e804752908
server
SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/thrombosis_prediction/thrombosis_prediction.sqlite | size=7327744
question set
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)
replay rule
R-ORD

the run this question belongs to

The JSON this page was rendered from