Triple
T37941356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 169 (segment through Fridley and Columbia Heights, before renumbering) |
E946495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former U.S. Highway segment |
C52492
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former U.S. Highway segment Context triple: [U.S. Route 169 (segment through Fridley and Columbia Heights, before renumbering), instanceOf, former U.S. Highway segment]
-
A.
former U.S. Highway alignment
chosen
A former U.S. Highway alignment is a roadway segment that once carried an official U.S. Highway designation but has since been rerouted, decommissioned, or reclassified under a different route or jurisdiction.
-
B.
former state highway designation
A former state highway designation is an official route number or name that was once assigned to a state-maintained roadway but has since been removed, reassigned, or decommissioned from the state highway system.
-
C.
former highway name
A former highway name is a historical designation once used to identify a specific roadway or route that has since been renumbered, renamed, decommissioned, or otherwise replaced in official records and signage.
-
D.
former freeway
A former freeway is a decommissioned high-speed roadway that has been removed, repurposed, or downgraded from its original limited-access highway function.
-
E.
former national road designation
A former national road designation identifies a roadway that was once part of a country's official national highway network but has since been reclassified, renumbered, or decommissioned.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.