Triple

T23087404
Position Surface form Disambiguated ID Type / Status
Subject Millerovo E575646 entity
Predicate railwayLine P848 FINISHED
Object Moscow–Rostov-on-Don 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–Rostov-on-Don line | Statement: [Millerovo, railwayLine, Moscow–Rostov-on-Don line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Moscow–Rostov-on-Don line
Context triple: [Millerovo, railwayLine, Moscow–Rostov-on-Don line]
  • A. Moscow–Voronezh line
    The Moscow–Voronezh line is a major Russian railway route connecting the capital Moscow with the city of Voronezh and serving as an important corridor for both passenger and freight traffic.
  • B. Belgorod–Moscow line
    The Belgorod–Moscow line is a major Russian railway route linking the city of Belgorod and the Belgorod Oblast region with the capital, Moscow, serving both passenger and freight traffic.
  • C. Nizhny Novgorod–Moscow line
    The Nizhny Novgorod–Moscow line is a major Russian railway route linking the capital Moscow with the important Volga city of Nizhny Novgorod, serving as a key corridor for both passenger and freight traffic.
  • D. Ryazhsk–Tula line
    The Ryazhsk–Tula line is a Russian railway route connecting the town of Ryazhsk with the city of Tula and forming part of a key regional transportation corridor.
  • E. Belgorod–Kharkiv line
    The Belgorod–Kharkiv line is an international railway route linking the Russian city of Belgorod with the Ukrainian city of Kharkiv, serving as a key transport corridor between the two countries.
  • 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–Rostov-on-Don line
Target entity description: The Moscow–Rostov-on-Don line is a major Russian railway route connecting the capital Moscow with the southern city of Rostov-on-Don, serving as a key corridor for both passenger and freight traffic.
  • A. Moscow–Voronezh line
    The Moscow–Voronezh line is a major Russian railway route connecting the capital Moscow with the city of Voronezh and serving as an important corridor for both passenger and freight traffic.
  • B. Belgorod–Moscow line
    The Belgorod–Moscow line is a major Russian railway route linking the city of Belgorod and the Belgorod Oblast region with the capital, Moscow, serving both passenger and freight traffic.
  • C. Nizhny Novgorod–Moscow line
    The Nizhny Novgorod–Moscow line is a major Russian railway route linking the capital Moscow with the important Volga city of Nizhny Novgorod, serving as a key corridor for both passenger and freight traffic.
  • D. Ryazhsk–Tula line
    The Ryazhsk–Tula line is a Russian railway route connecting the town of Ryazhsk with the city of Tula and forming part of a key regional transportation corridor.
  • E. Belgorod–Kharkiv line
    The Belgorod–Kharkiv line is an international railway route linking the Russian city of Belgorod with the Ukrainian city of Kharkiv, serving as a key transport corridor between the two countries.
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da652ac819085919ade6dd7bce4 completed April 29, 2026, 4:48 a.m.
Created at: April 17, 2026, 3:57 p.m.