Triple
T622681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Front Range Urban Corridor |
E14547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban corridor |
C2952
|
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 corridor Context triple: [Front Range Urban Corridor, instanceOf, urban corridor]
-
A.
development corridor
A development corridor is a strategically planned geographic area, often aligned along major transportation routes, where concentrated investment in infrastructure, industry, and services is used to stimulate economic growth and regional integration.
-
B.
transport corridor
chosen
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.
-
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.
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.
-
E.
urban plaza
An urban plaza is a publicly accessible open space within a city, typically surrounded by buildings and streets, designed to support social interaction, circulation, and civic activities.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.