Triple
T36456147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkinskaya–Chekhovskaya–Tverskaya interchange node |
E898156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Moscow Metro transfer complex |
C62679
|
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: Moscow Metro transfer complex Context triple: [Pushkinskaya–Chekhovskaya–Tverskaya interchange node, instanceOf, Moscow Metro transfer complex]
-
A.
Moscow Central Circle station
A Moscow Central Circle station is a passenger rail facility on Moscow's orbital urban rail line that provides platforms, services, and access for trains and commuters within the city's integrated transit network.
-
B.
Moscow Monorail station
A Moscow Monorail station is a designated stop along the Moscow Monorail system where passengers can board, alight, and transfer between monorail trains and other modes of public transportation.
-
C.
Moscow Metro depot
A Moscow Metro depot is a specialized facility where metro trains are stored, inspected, maintained, and repaired to ensure reliable operation of the Moscow subway system.
-
D.
Moscow Central Diameters line
The Moscow Central Diameters line is a suburban rail transit route in Moscow that operates like an urban through-running commuter line, connecting outlying areas across the city via upgraded existing railway corridors.
-
E.
Sofia Metro station
A Sofia Metro station is an underground or surface transit facility within the Sofia Metro system that provides platforms, access points, and related infrastructure for boarding, alighting, and transferring between metro trains.
- F. None of above. chosen
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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.