Triple

T20242178
Position Surface form Disambiguated ID Type / Status
Subject Aschersleben station E498324 entity
Predicate railwayLine P848 FINISHED
Object Halle–Vienenburg 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: Halle–Vienenburg railway | Statement: [Aschersleben station, railwayLine, Halle–Vienenburg railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Halle–Vienenburg railway
Context triple: [Aschersleben station, railwayLine, Halle–Vienenburg railway]
  • A. 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.
  • 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. Halle–Cottbus railway
    The Halle–Cottbus railway is a major German rail line in eastern Germany that connects the city of Halle (Saale) with Cottbus, serving both regional and long-distance passenger and freight traffic.
  • D. Nuremberg–Bamberg railway
    The Nuremberg–Bamberg railway is a major German main line in Bavaria that connects the cities of Nuremberg and Bamberg and forms part of important regional and long-distance rail routes.
  • E. Halle–Halberstadt railway
    The Halle–Halberstadt railway is a major rail line in central Germany connecting the city of Halle (Saale) with Halberstadt and serving as an important regional and long-distance transport corridor.
  • 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: Halle–Vienenburg railway
Target entity description: The Halle–Vienenburg railway is a historic rail line in central Germany that connects the city of Halle (Saale) with Vienenburg, passing through various towns in Saxony-Anhalt and Lower Saxony.
  • A. 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.
  • 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. Halle–Cottbus railway
    The Halle–Cottbus railway is a major German rail line in eastern Germany that connects the city of Halle (Saale) with Cottbus, serving both regional and long-distance passenger and freight traffic.
  • D. Nuremberg–Bamberg railway
    The Nuremberg–Bamberg railway is a major German main line in Bavaria that connects the cities of Nuremberg and Bamberg and forms part of important regional and long-distance rail routes.
  • E. Halle–Halberstadt railway
    The Halle–Halberstadt railway is a major rail line in central Germany connecting the city of Halle (Saale) with Halberstadt and serving as an important regional and long-distance transport corridor.
  • 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_69da6274c58c81909c646eabed6f4f30 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6716f9d248190a145f6883827ebbe completed April 20, 2026, 6:33 p.m.
Created at: April 11, 2026, 11:40 p.m.