Triple

T17098570
Position Surface form Disambiguated ID Type / Status
Subject Kievsky suburban direction E414914 entity
Predicate terminus P388 FINISHED
Object Moscow Kievsky railway terminal — NE NERFINISHED

How this triple was built (3 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: Moscow Kievsky railway terminal | Statement: [Kievsky suburban direction, terminus, Moscow Kievsky railway terminal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Moscow Kievsky railway terminal
Context triple: [Kievsky suburban direction, terminus, Moscow Kievsky railway terminal]
  • A. Moscow Yaroslavsky railway terminal
    Moscow Yaroslavsky railway terminal is one of the main railway stations in Moscow and the primary departure point for trains on the Trans-Siberian Railway and routes to Russia’s Far East.
  • B. Moscow Kursky railway station
    Moscow Kursky railway station is one of Moscow’s largest and busiest rail terminals, serving major long-distance, suburban, and international routes, particularly toward southern and eastern destinations.
  • C. Moskovsky Rail Terminal
    Moskovsky Rail Terminal is one of Saint Petersburg’s main railway stations, serving long-distance and high-speed trains, including routes to Moscow and other major Russian cities.
  • D. Moscow Kazansky railway station
    Moscow Kazansky railway station is one of Moscow’s largest and busiest rail terminals, serving as a major hub for long-distance trains to Russia’s Volga, Ural, and Central Asian regions.
  • E. Moscow Savyolovsky railway station
    Moscow Savyolovsky railway station is one of Moscow’s main rail terminals, serving suburban and regional trains primarily to the north of the city.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Moscow Kievsky railway terminal
Target entity description: Moscow Kievsky railway terminal is one of Moscow’s major railway stations, serving long-distance and suburban trains—particularly those heading southwest toward Ukraine and Europe.
  • A. Moscow Yaroslavsky railway terminal
    Moscow Yaroslavsky railway terminal is one of the main railway stations in Moscow and the primary departure point for trains on the Trans-Siberian Railway and routes to Russia’s Far East.
  • B. Moscow Kursky railway station
    Moscow Kursky railway station is one of Moscow’s largest and busiest rail terminals, serving major long-distance, suburban, and international routes, particularly toward southern and eastern destinations.
  • C. Moskovsky Rail Terminal
    Moskovsky Rail Terminal is one of Saint Petersburg’s main railway stations, serving long-distance and high-speed trains, including routes to Moscow and other major Russian cities.
  • D. Moscow Kazansky railway station
    Moscow Kazansky railway station is one of Moscow’s largest and busiest rail terminals, serving as a major hub for long-distance trains to Russia’s Volga, Ural, and Central Asian regions.
  • E. Moscow Savyolovsky railway station
    Moscow Savyolovsky railway station is one of Moscow’s main rail terminals, serving suburban and regional trains primarily to the north of the city.
  • F. None of above. chosen

Provenance (2 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbffafb08190baf9e0b4fdf1b404 completed April 18, 2026, 7:31 p.m.
Created at: April 10, 2026, 5:35 a.m.