Triple
T25400861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | interchange with London Underground at Walthamstow Central |
E636412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway–Underground interchange |
C17128
|
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: railway–Underground interchange Context triple: [interchange with London Underground at Walthamstow Central, instanceOf, railway–Underground interchange]
-
A.
railway–metro interchange
chosen
A railway–metro interchange is a transport facility where mainline railway services and urban metro lines connect, enabling passengers to transfer conveniently between regional and local rail networks.
-
B.
group of metro interchange stations
A group of metro interchange stations is a collection of transit hubs where multiple metro lines intersect, enabling passengers to transfer between routes within an urban rail network.
-
C.
London Underground interchange
A London Underground interchange is a station or complex where passengers can transfer between two or more Underground lines (and sometimes other rail services) within a single integrated facility.
-
D.
railway junction
A railway junction is a point on a rail network where two or more railway lines meet or diverge, allowing trains to switch between different routes.
-
E.
underground rail corridor
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:50 p.m.