Triple
T32569073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhdanovskaya station |
E832458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Moscow Metro station |
C57575
|
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: former Moscow Metro station Context triple: [Zhdanovskaya station, instanceOf, former Moscow Metro station]
-
A.
former line of the Moscow Metro
A former line of the Moscow Metro is a decommissioned or restructured rapid transit route that once operated within the Moscow Metro system but has since been closed, merged, or renumbered.
-
B.
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.
-
C.
станция Московского метрополитена
chosen
Станция Московского метрополитена — это элемент транспортной инфраструктуры подземной или наземной линии метро, предназначенный для посадки и высадки пассажиров, пересадки между линиями и обеспечения доступа к городским объектам.
-
D.
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.
-
E.
Minsk Metro station
A Minsk Metro station is an underground or surface transit facility within the Minsk Metro system that provides platforms, access points, and passenger services for boarding and alighting metro trains.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:03 a.m.