Triple
T33524646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 490 (Illinois) |
E858604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned auxiliary Interstate highway |
C528
|
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: planned auxiliary Interstate highway Context triple: [Interstate 490 (Illinois), instanceOf, planned auxiliary Interstate highway]
-
A.
auxiliary Interstate Highway
chosen
An auxiliary Interstate Highway is a shorter, supplementary route connected to a primary Interstate that typically serves to bypass, loop around, or provide direct access to urban areas.
-
B.
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.
-
C.
Interstate business loop
An Interstate business loop is a special route that departs from an Interstate Highway to pass through the downtown or commercial center of a nearby city before reconnecting with the same Interstate.
-
D.
planned expressway
A planned expressway is a proposed high-speed, limited-access roadway that has been formally designed and approved but not yet constructed or opened to traffic.
-
E.
interstate highway system component
An interstate highway system component is any physical or functional element—such as roadways, interchanges, signage, or support infrastructure—that collectively enables the operation, connectivity, and safety of the national interstate highway network.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.