Triple
T12901034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-76 corridor through Philadelphia |
E308611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban freeway segment |
C1129
|
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: urban freeway segment Context triple: [I-76 corridor through Philadelphia, instanceOf, urban freeway segment]
-
A.
highway segment
chosen
A highway segment is a continuous portion of a highway between two defined endpoints, such as interchanges, intersections, or mile markers, characterized by consistent physical and operational attributes.
-
B.
road segment
A road segment is a continuous portion of a roadway between two defined endpoints, such as intersections or junctions, characterized by uniform attributes like direction, number of lanes, and speed limit.
-
C.
urban arterial road
An urban arterial road is a high-capacity city street designed to carry large volumes of traffic efficiently between local streets and major highways while providing controlled access to adjacent land uses.
-
D.
urban beltway
An urban beltway is a high-capacity circumferential highway or roadway system that encircles a city to route traffic around its core, reduce congestion, and connect radial routes and suburbs.
-
E.
elevated expressway
An elevated expressway is a high-capacity roadway built on raised structures above ground level to allow uninterrupted traffic flow over urban streets, railways, or other obstacles.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:40 p.m.