Triple
T38533833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tretyakovskaya–Novokuznetskaya transfer passage |
E923442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metro transfer corridor |
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: metro transfer corridor Context triple: [Tretyakovskaya–Novokuznetskaya transfer passage, instanceOf, metro transfer corridor]
-
A.
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.
-
B.
metro train
A metro train is an electrically powered, multi-car rail vehicle designed to transport large numbers of passengers quickly and frequently along dedicated urban and suburban transit lines.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
metro network
A metro network is an interconnected system of urban rail lines, stations, and supporting infrastructure designed to transport large numbers of passengers efficiently within and around a city.
-
E.
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.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.