Triple
T11514766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James White Parkway bridge area |
E273002
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | roadway and bridge corridor |
C2978
|
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: roadway and bridge corridor Context triple: [James White Parkway bridge area, instanceOf, roadway and bridge corridor]
-
A.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
B.
road infrastructure
chosen
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
C.
highway bridge
A highway bridge is a raised structure that carries vehicular traffic over obstacles such as rivers, valleys, other roads, or railways, ensuring continuous and efficient roadway connectivity.
-
D.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:36 p.m.