Triple
T19306124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmstedt |
E482831
|
entity |
| Predicate | hasTransportConnection |
P845
|
FINISHED |
| Object | railway line Braunschweig–Magdeburg |
—
|
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: railway line Braunschweig–Magdeburg | Statement: [Helmstedt, hasTransportConnection, railway line Braunschweig–Magdeburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: railway line Braunschweig–Magdeburg Context triple: [Helmstedt, hasTransportConnection, railway line Braunschweig–Magdeburg]
-
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.
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.
-
C.
Hanover–Göttingen railway line
The Hanover–Göttingen railway line is a major rail route in Lower Saxony, Germany, connecting the cities of Hanover and Göttingen and serving numerous intermediate towns.
-
D.
Naumburg–Jena railway
The Naumburg–Jena railway is a regional rail line in the German state of Thuringia that connects the historic city of Naumburg with the university city of Jena along the Saale River.
-
E.
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.
- 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: railway line Braunschweig–Magdeburg Target entity description: The Braunschweig–Magdeburg railway line is a major rail route in central Germany that connects the cities of Braunschweig and Magdeburg and serves as an important regional and intercity 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.
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.
-
C.
Hanover–Göttingen railway line
The Hanover–Göttingen railway line is a major rail route in Lower Saxony, Germany, connecting the cities of Hanover and Göttingen and serving numerous intermediate towns.
-
D.
Naumburg–Jena railway
The Naumburg–Jena railway is a regional rail line in the German state of Thuringia that connects the historic city of Naumburg with the university city of Jena along the Saale River.
-
E.
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.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604c84fe08190869463bdd0324160 |
completed | April 20, 2026, 10:49 a.m. |
Created at: April 10, 2026, 1:31 p.m.