Triple

T18621710
Position Surface form Disambiguated ID Type / Status
Subject Sangerhausen E455166 entity
Predicate railwayConnection P848 FINISHED
Object Magdeburg–Erfurt railway — 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: Magdeburg–Erfurt railway | Statement: [Sangerhausen, railwayConnection, Magdeburg–Erfurt railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Magdeburg–Erfurt railway
Context triple: [Sangerhausen, railwayConnection, Magdeburg–Erfurt railway]
  • A. Magdeburg–Thale railway
    The Magdeburg–Thale railway is a German rail line in Saxony-Anhalt that connects the city of Magdeburg with the town of Thale in the Harz region, serving both regional passenger and freight traffic.
  • B. Halle–Magdeburg railway
    The Halle–Magdeburg railway is a major rail line in central Germany that connects the cities of Halle (Saale) and Magdeburg, serving as an important regional and long-distance transport corridor.
  • C. Berlin–Magdeburg railway
    The Berlin–Magdeburg railway is a major German rail line connecting the capital city Berlin with the city of Magdeburg, serving both regional and long-distance passenger and freight traffic.
  • D. Halle–Leipzig railway
    The Halle–Leipzig railway is a major German rail line in Saxony-Anhalt and Saxony that connects the cities of Halle (Saale) and Leipzig and forms part of an important regional and long-distance transport corridor.
  • E. Berlin–Dresden railway
    The Berlin–Dresden railway is a major German mainline rail route connecting the capital Berlin with the city of Dresden, serving both long-distance and regional passenger traffic.
  • 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: Magdeburg–Erfurt railway
Target entity description: The Magdeburg–Erfurt railway is a major German rail line in central Germany that connects the cities of Magdeburg and Erfurt, serving as an important regional and long-distance transport corridor.
  • A. Magdeburg–Thale railway
    The Magdeburg–Thale railway is a German rail line in Saxony-Anhalt that connects the city of Magdeburg with the town of Thale in the Harz region, serving both regional passenger and freight traffic.
  • B. Halle–Magdeburg railway
    The Halle–Magdeburg railway is a major rail line in central Germany that connects the cities of Halle (Saale) and Magdeburg, serving as an important regional and long-distance transport corridor.
  • C. Berlin–Magdeburg railway
    The Berlin–Magdeburg railway is a major German rail line connecting the capital city Berlin with the city of Magdeburg, serving both regional and long-distance passenger and freight traffic.
  • D. Halle–Leipzig railway
    The Halle–Leipzig railway is a major German rail line in Saxony-Anhalt and Saxony that connects the cities of Halle (Saale) and Leipzig and forms part of an important regional and long-distance transport corridor.
  • E. Berlin–Dresden railway
    The Berlin–Dresden railway is a major German mainline rail route connecting the capital Berlin with the city of Dresden, serving both long-distance and regional passenger traffic.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f0146f48190a872032db6e660c6 completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.