Triple
T4650692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London to Worthing corridor |
E102286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport axis |
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: transport axis Context triple: [London to Worthing corridor, instanceOf, transport axis]
-
A.
transport symbol
A transport symbol is a standardized visual icon or sign that conveys information about transportation modes, routes, services, or regulations to facilitate safe and efficient travel.
-
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.
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.
-
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.
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.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:14 p.m.