Triple

T17003614
Position Surface form Disambiguated ID Type / Status
Subject Kazansky suburban direction E412510 entity
Predicate primaryStationInMoscow P394 FINISHED
Object Moscow Kazansky railway station E766011 NE FINISHED

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 Kazansky railway station | Statement: [Kazansky suburban direction, primaryStationInMoscow, Moscow Kazansky railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscow Kazansky railway station
Context triple: [Kazansky suburban direction, primaryStationInMoscow, Moscow Kazansky railway station]
  • A. Moscow Kazansky railway station chosen
    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.
  • 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. Moscow Rizhsky railway station
    Moscow Rizhsky railway station is one of Moscow’s main railway terminals, serving suburban and long-distance trains—particularly toward Latvia and the northwestern regions of Russia.
  • D. 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.
  • E. Moscow Yaroslavsky railway station
    Moscow Yaroslavsky railway station is one of Moscow’s major rail terminals and the primary departure point for long-distance trains to Russia’s northeast and Siberia, including the Trans-Siberian Railway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryStationInMoscow
Context triple: [Kazansky suburban direction, primaryStationInMoscow, Moscow Kazansky railway station]
  • A. primaryStationInRussia
    Indicates that the referenced station serves as the main or principal station located within the territory of Russia.
  • B. primaryStation chosen
    Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
  • C. otherMoscowAirport
    Indicates that one airport is another airport located in Moscow, distinguishing between multiple Moscow-area airports.
  • D. isLocatedRelativeToMoscow
    Indicates a spatial relationship specifying where an entity is situated in relation to the city of Moscow.
  • E. otherMajorMoscowAirports
    Indicates that the referenced airports are major airports serving Moscow other than the primary one under consideration.
  • F. None of above.

Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d380f968819097b59e7bac333ea4 completed April 18, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01673e1be08190b39c38fd8115a02c completed May 11, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69e35d552bc08190af17ef7659e094ef completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:32 a.m.