Triple
T34581066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Central Diameters |
E887902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-city rail network |
C3549
|
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: cross-city rail network Context triple: [Moscow Central Diameters, instanceOf, cross-city rail network]
-
A.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
-
B.
railway network
chosen
A railway network is an interconnected system of tracks, stations, signaling, and rolling stock that enables the organized movement of trains between multiple locations.
-
C.
cross-London rail system
A cross-London rail system is an integrated network of rail lines and tunnels that traverse the city from one side to the other, providing high-capacity, rapid transit across central London and connecting outer suburbs.
-
D.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
E.
commuter rail infrastructure
Commuter rail infrastructure comprises the physical and operational systems—such as tracks, stations, signaling, power, and maintenance facilities—designed to support frequent, reliable passenger train service between suburbs and urban centers.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.