Triple
T21299406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoogeveen |
E525014
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Zwolle–Groningen 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: Zwolle–Groningen railway | Statement: [Hoogeveen, railwayLine, Zwolle–Groningen railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zwolle–Groningen railway Context triple: [Hoogeveen, railwayLine, Zwolle–Groningen railway]
-
A.
Leeuwarden–Groningen railway
The Leeuwarden–Groningen railway is a regional rail line in the northern Netherlands that connects the cities of Leeuwarden and Groningen through several intermediate towns.
-
B.
Utrecht–Zwolle railway
The Utrecht–Zwolle railway is a major rail corridor in the Netherlands connecting the central hub of Utrecht with the northern city of Zwolle, serving as an important route for both regional and intercity train services.
-
C.
Zwolle–Meppel railway
The Zwolle–Meppel railway is a key rail route in the Netherlands that connects the city of Zwolle with Meppel and forms part of important national and international train services.
-
D.
Zwolle–Almelo railway
The Zwolle–Almelo railway is a Dutch rail line in the eastern Netherlands that connects the city of Zwolle with Almelo and forms part of the regional and intercity rail network.
-
E.
Zwolle–Leeuwarden railway
The Zwolle–Leeuwarden railway is a mainline rail route in the Netherlands that connects the city of Zwolle with the provincial capital Leeuwarden, serving as an important regional passenger corridor in the north of the country.
- 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: Zwolle–Groningen railway Target entity description: The Zwolle–Groningen railway is a major rail route in the northeastern Netherlands that connects the city of Zwolle with Groningen, serving several intermediate towns and facilitating regional passenger and freight transport.
-
A.
Leeuwarden–Groningen railway
The Leeuwarden–Groningen railway is a regional rail line in the northern Netherlands that connects the cities of Leeuwarden and Groningen through several intermediate towns.
-
B.
Utrecht–Zwolle railway
The Utrecht–Zwolle railway is a major rail corridor in the Netherlands connecting the central hub of Utrecht with the northern city of Zwolle, serving as an important route for both regional and intercity train services.
-
C.
Zwolle–Meppel railway
The Zwolle–Meppel railway is a key rail route in the Netherlands that connects the city of Zwolle with Meppel and forms part of important national and international train services.
-
D.
Zwolle–Almelo railway
The Zwolle–Almelo railway is a Dutch rail line in the eastern Netherlands that connects the city of Zwolle with Almelo and forms part of the regional and intercity rail network.
-
E.
Zwolle–Leeuwarden railway
The Zwolle–Leeuwarden railway is a mainline rail route in the Netherlands that connects the city of Zwolle with the provincial capital Leeuwarden, serving as an important regional passenger corridor in the north of the country.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385b1c548190b940ded0163ee3ca |
completed | April 21, 2026, 8:42 a.m. |
Created at: April 16, 2026, 4:05 p.m.