Triple
T8226041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Quarter transport axis (extended) |
E192174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban transport axis |
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 transport axis Context triple: [European Quarter transport axis (extended), instanceOf, urban transport axis]
-
A.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
B.
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.
-
C.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
D.
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.
-
E.
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.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:45 p.m.