Triple
T28597383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsway (Burnaby) corridor |
E723810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban arterial road corridor |
C1347
|
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 arterial road corridor Context triple: [Kingsway (Burnaby) corridor, instanceOf, urban arterial road corridor]
-
A.
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.
-
B.
arterial roadway
An arterial roadway is a high-capacity urban or suburban street designed to efficiently carry large volumes of through traffic between local streets and highways while providing limited direct property access.
-
C.
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.
-
D.
road transportation corridor
chosen
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.
-
E.
civic thoroughfare
A civic thoroughfare is a major public street or corridor designed to accommodate high volumes of movement while structuring and showcasing key civic, cultural, and institutional functions of a community.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:22 a.m.