Triple
T10124949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Birmingham transport corridor |
E226188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic transport route |
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: strategic transport route Context triple: [London–Birmingham transport corridor, instanceOf, strategic transport route]
-
A.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
-
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.
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.
-
D.
transport strategy
A transport strategy is a high-level plan that defines how people and goods will be moved efficiently, safely, sustainably, and cost-effectively within and between areas over a given time horizon.
-
E.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:05 p.m.