Triple

T10930787
Position Surface form Disambiguated ID Type / Status
Subject Kurskaya E258198 entity
Predicate namedAfter P63 FINISHED
Object Kursky railway station E910983 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Kursky railway station | Statement: [Kurskaya, namedAfter, Kursky railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kursky railway station
Context triple: [Kurskaya, namedAfter, Kursky railway station]
  • A. Kursky railway station chosen
    Kursky railway station is one of Moscow’s major railway terminals, serving long-distance and suburban trains, particularly on routes toward Kursk and southern Russia.
  • B. Krasnoselskaya station
    Krasnoselskaya station is a Moscow Metro station known for its early Soviet-era architecture and location on the system’s first metro line.
  • C. Kachinskaya station
    Kachinskaya station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
  • D. Komsomolskaya station
    Komsomolskaya station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
  • E. Komsomolskaya station
    Komsomolskaya station is a prominent Moscow Metro station known for its grand Stalinist architecture and location beneath Komsomolskaya Square, a major railway hub.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7709f92088190a15ae3638d3b14fb completed April 9, 2026, 9:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e4cbce653481909b201a2d5871e129 completed April 19, 2026, 12:34 p.m.
Created at: April 8, 2026, 9:22 p.m.