Triple
T38134096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Tube for London (planned for Central line) |
E952299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deep-level tube train design |
C30576
|
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: deep-level tube train design Context triple: [New Tube for London (planned for Central line), instanceOf, deep-level tube train design]
-
A.
deep-level tube railway
A deep-level tube railway is an underground urban rail system constructed in small-diameter tunnels bored far below street level, typically using electric trains and serving high-density city corridors.
-
B.
deep-level tube stock
chosen
Deep-level tube stock is a type of railway rolling stock specifically designed for small-diameter, deep-bored tunnels, typically featuring narrow, cylindrical car bodies and high-performance traction suited to steep gradients and tight curves.
-
C.
railway vehicle design
Railway vehicle design is the engineering discipline focused on conceptualizing, developing, and optimizing rail vehicles for performance, safety, comfort, and compatibility with railway infrastructure and operations.
-
D.
elevated railway
An elevated railway is a rail transport system in which tracks and stations are built on raised structures above ground level, typically supported by columns or girders, to avoid interference with street traffic.
-
E.
maglev railway line
A maglev railway line is a transportation route equipped with magnetic levitation and guidance systems that enable high-speed, low-friction train travel along a dedicated track.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.