Triple
T23221959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teterow |
E580917
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Güstrow–Teterow 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: Güstrow–Teterow railway | Statement: [Teterow, railwayLine, Güstrow–Teterow railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Güstrow–Teterow railway Context triple: [Teterow, railwayLine, Güstrow–Teterow railway]
-
A.
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.
-
B.
Berlin–Rostock railway
The Berlin–Rostock railway is a major German rail line connecting the capital city Berlin with the Baltic Sea port of Rostock, serving as an important route for both passenger and freight traffic in northeastern Germany.
-
C.
Berlin–Stralsund railway
The Berlin–Stralsund railway is a major rail line in northeastern Germany that connects the capital Berlin with the Baltic Sea port city of Stralsund, serving as an important route for both regional and long-distance traffic.
-
D.
Dresden–Görlitz railway
The Dresden–Görlitz railway is a major railway line in the German state of Saxony that connects the city of Dresden with the border town of Görlitz, serving as an important regional and international transport corridor.
-
E.
Stralsund–Sassnitz railway
The Stralsund–Sassnitz railway is a key rail line in northeastern Germany that connects the mainland city of Stralsund with the Baltic Sea island of Rügen and its ferry port at Sassnitz.
- 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: Güstrow–Teterow railway Target entity description: The Güstrow–Teterow railway is a regional rail line in the German state of Mecklenburg-Vorpommern that connects the towns of Güstrow and Teterow.
-
A.
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.
-
B.
Berlin–Rostock railway
The Berlin–Rostock railway is a major German rail line connecting the capital city Berlin with the Baltic Sea port of Rostock, serving as an important route for both passenger and freight traffic in northeastern Germany.
-
C.
Berlin–Stralsund railway
The Berlin–Stralsund railway is a major rail line in northeastern Germany that connects the capital Berlin with the Baltic Sea port city of Stralsund, serving as an important route for both regional and long-distance traffic.
-
D.
Dresden–Görlitz railway
The Dresden–Görlitz railway is a major railway line in the German state of Saxony that connects the city of Dresden with the border town of Görlitz, serving as an important regional and international transport corridor.
-
E.
Stralsund–Sassnitz railway
The Stralsund–Sassnitz railway is a key rail line in northeastern Germany that connects the mainland city of Stralsund with the Baltic Sea island of Rügen and its ferry port at Sassnitz.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922924308190a26b00e09ce60ecd |
completed | April 29, 2026, 5:07 a.m. |
Created at: April 17, 2026, 4:08 p.m.