Triple
T17393824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halle (Saale) Hauptbahnhof |
E422897
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Halle–Cottbus 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–Cottbus railway | Statement: [Halle (Saale) Hauptbahnhof, railwayLine, Halle–Cottbus railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Halle–Cottbus railway Context triple: [Halle (Saale) Hauptbahnhof, railwayLine, Halle–Cottbus 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.
Berlin–Görlitz railway
The Berlin–Görlitz railway is a major German rail line connecting Berlin with the city of Görlitz near the Polish border, serving both regional and long-distance passenger and freight traffic.
-
C.
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.
-
D.
Berlin–Halle railway
The Berlin–Halle railway is a major German rail route connecting the capital Berlin with the city of Halle, serving as an important corridor for both passenger and freight traffic.
-
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–Cottbus railway Target entity description: 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.
-
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.
Berlin–Görlitz railway
The Berlin–Görlitz railway is a major German rail line connecting Berlin with the city of Görlitz near the Polish border, serving both regional and long-distance passenger and freight traffic.
-
C.
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.
-
D.
Berlin–Halle railway
The Berlin–Halle railway is a major German rail route connecting the capital Berlin with the city of Halle, serving as an important corridor for both passenger and freight traffic.
-
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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abbd84881908af91bb7c9784026 |
completed | April 19, 2026, 2:15 a.m. |
Created at: April 10, 2026, 5:45 a.m.