Triple

T32276033
Position Surface form Disambiguated ID Type / Status
Subject станция метро «Кузьминки» E824547 entity
Predicate instanceOf P0 FINISHED
Object станция Московского метрополитена 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: станция Московского метрополитена
Context triple: [станция метро «Кузьминки», instanceOf, станция Московского метрополитена]
  • A. станция Московского метрополитена chosen
    Станция Московского метрополитена — это элемент транспортной инфраструктуры подземной или наземной линии метро, предназначенный для посадки и высадки пассажиров, пересадки между линиями и обеспечения доступа к городским объектам.
  • B. станция Петербургского метрополитена
    Станция Петербургского метрополитена — это подземный или наземный транспортный узел в системе метро Санкт‑Петербурга, предназначенный для посадки и высадки пассажиров, пересадки между линиями и обеспечения доступа к городской инфраструктуре.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69f3490f404081908450db66884f4334 completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:43 a.m.