Datasets:
Add valuesets_ddl.sql
Browse files- valuesets_ddl.sql +24 -0
valuesets_ddl.sql
ADDED
|
@@ -0,0 +1,24 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
-- Terminology lookup table -- ABLATION FRAGMENT, NOT PART OF THE FROZEN SCHEMA.
|
| 2 |
+
--
|
| 3 |
+
-- IMPORTANT: this block was NOT present in schema/schema.sql during the published
|
| 4 |
+
-- training and evaluation runs. The `valuesets` table existed in both DuckDB
|
| 5 |
+
-- databases and every gold query resolved terminology through it, but its DDL was
|
| 6 |
+
-- never shown to the model -- fine-tuned models learned its columns implicitly from
|
| 7 |
+
-- thousands of training targets, while the frozen baseline had only the table name
|
| 8 |
+
-- to go on.
|
| 9 |
+
--
|
| 10 |
+
-- valuesets_ablation.ipynb prepends this fragment to schema.sql and re-runs the
|
| 11 |
+
-- held-out evaluation on the published checkpoints, to measure how much of the
|
| 12 |
+
-- frozen model's failure is attributable to the missing table description rather
|
| 13 |
+
-- than to reasoning ability. See PAPER.md Section 5.6.
|
| 14 |
+
--
|
| 15 |
+
-- Do NOT merge this into schema.sql: doing so would break correspondence between
|
| 16 |
+
-- the committed schema and the runs reported in the paper.
|
| 17 |
+
|
| 18 |
+
CREATE TABLE valuesets (
|
| 19 |
+
table_name VARCHAR, -- which fact table this concept belongs to
|
| 20 |
+
code VARCHAR,
|
| 21 |
+
code_system VARCHAR, -- joins against that table's `system`-suffixed column
|
| 22 |
+
display VARCHAR, -- human-readable concept name; the ILIKE search target
|
| 23 |
+
lookup_ambiguous BOOLEAN -- display text matches >1 row in the same table under ILIKE containment
|
| 24 |
+
);
|