Triple
T13581961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan State Highway 35 |
E324440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former state trunkline highway |
C10921
|
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 state trunkline highway Context triple: [Michigan State Highway 35, instanceOf, former state trunkline highway]
-
A.
former state highway designation
chosen
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.
-
B.
former national highway of India
A former national highway of India is a roadway that was once part of the country's officially designated national highway network but has since been renumbered, reclassified, or decommissioned from that status.
-
C.
Interstate Highway
An Interstate Highway is a high-capacity, limited-access roadway that forms part of a nationwide network designed to support efficient long-distance and high-speed vehicular travel between major cities and regions.
-
D.
state highway
A state highway is a public road maintained and administered by a state government, forming part of a regional or statewide transportation network that connects cities, towns, and other major routes.
-
E.
U.S. Numbered Highway
A U.S. Numbered Highway is a nationally coordinated, signed roadway within the United States that is part of the United States Numbered Highway System, providing intercity and interstate connections but distinct from the Interstate Highway System.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:48 p.m.