Triple

T20028995
Position Surface form Disambiguated ID Type / Status
Subject Podolsk railway station E495069 entity
Predicate locatedOnLine P2409 FINISHED
Object Moscow–Tula railway line — 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–Tula railway line | Statement: [Podolsk railway station, locatedOnLine, Moscow–Tula railway line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Moscow–Tula railway line
Context triple: [Podolsk railway station, locatedOnLine, Moscow–Tula railway line]
  • A. Moscow–Yaroslavl railway line
    The Moscow–Yaroslavl railway line is a major rail route in Russia connecting Moscow with the historic city of Yaroslavl and serving as part of the broader network linking the capital to the northeast.
  • B. Moscow–Ryazan line
    The Moscow–Ryazan line is a major Russian railway route connecting Moscow with the city of Ryazan and serving numerous suburban and regional destinations along the way.
  • C. Moscow–Samara railway line
    The Moscow–Samara railway line is a major Russian rail route connecting the capital Moscow with the Volga city of Samara, serving as an important corridor for both passenger and freight transport.
  • D. Moscow–Bryansk railway
    The Moscow–Bryansk railway is a major rail line in western Russia that connects Moscow with the city of Bryansk, forming part of an important route toward Ukraine and southwestern regions.
  • E. Moscow–Kursk railway line
    The Moscow–Kursk railway line is a major rail route in western Russia that connects Moscow with the city of Kursk and serves numerous intermediate towns and suburbs.
  • 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–Tula railway line
Target entity description: The Moscow–Tula railway line is a major rail route in western Russia that connects the capital city of Moscow with the industrial city of Tula, serving numerous commuter and regional trains.
  • A. Moscow–Yaroslavl railway line
    The Moscow–Yaroslavl railway line is a major rail route in Russia connecting Moscow with the historic city of Yaroslavl and serving as part of the broader network linking the capital to the northeast.
  • B. Moscow–Ryazan line
    The Moscow–Ryazan line is a major Russian railway route connecting Moscow with the city of Ryazan and serving numerous suburban and regional destinations along the way.
  • C. Moscow–Samara railway line
    The Moscow–Samara railway line is a major Russian rail route connecting the capital Moscow with the Volga city of Samara, serving as an important corridor for both passenger and freight transport.
  • D. Moscow–Bryansk railway
    The Moscow–Bryansk railway is a major rail line in western Russia that connects Moscow with the city of Bryansk, forming part of an important route toward Ukraine and southwestern regions.
  • E. Moscow–Kursk railway line
    The Moscow–Kursk railway line is a major rail route in western Russia that connects Moscow with the city of Kursk and serves numerous intermediate towns and suburbs.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662908df081909a6c8ccf0dd90fff completed April 20, 2026, 5:29 p.m.
Created at: April 11, 2026, 3:36 p.m.