Triple
T35123360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 101 Bypass (California) |
E1014225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former highway alignment |
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 highway alignment Context triple: [U.S. Route 101 Bypass (California), instanceOf, former highway alignment]
-
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 road bypass
A former road bypass is a roadway that was originally constructed to divert through-traffic around a town or congested area but has since been decommissioned, reclassified, or repurposed so it no longer functions as the primary bypass route.
-
C.
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.
-
D.
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.
-
E.
road alignment
Road alignment is the planned horizontal and vertical positioning of a roadway’s centerline to achieve safe, efficient, and economical traffic movement within given terrain and design constraints.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.