Triple
T22155248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N35 road |
E547517
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Zwolle–Enschede route |
—
|
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–Enschede route | Statement: [N35 road, hasAlternativeName, Zwolle–Enschede route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zwolle–Enschede route Context triple: [N35 road, hasAlternativeName, Zwolle–Enschede route]
-
A.
Nijmegen–Oss corridor
The Nijmegen–Oss corridor is a key Dutch transport axis linking the cities of Nijmegen and Oss and serving intermediate municipalities such as Wijchen.
-
B.
Lelystad–Enkhuizen route
The Lelystad–Enkhuizen route is a Dutch transport corridor across the IJsselmeer that links the cities of Lelystad and Enkhuizen via a major causeway.
-
C.
Haarlem–Leiden corridor
The Haarlem–Leiden corridor is a key transport axis in the western Netherlands linking the cities of Haarlem and Leiden through a network of roads and other infrastructure.
-
D.
Leiden–Alphen–Utrecht corridor
The Leiden–Alphen–Utrecht corridor is a Dutch railway line connecting the cities of Leiden, Alphen aan den Rijn, and Utrecht as part of the Randstad region’s regional rail network.
-
E.
Amsterdam–Alkmaar corridor
The Amsterdam–Alkmaar corridor is a major transport axis in the Netherlands linking the Amsterdam metropolitan area with the city of Alkmaar through a network of roads and other infrastructure.
- 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–Enschede route Target entity description: The Zwolle–Enschede route is a major east–west roadway in the Netherlands connecting the city of Zwolle with Enschede through the province of Overijssel.
-
A.
Nijmegen–Oss corridor
The Nijmegen–Oss corridor is a key Dutch transport axis linking the cities of Nijmegen and Oss and serving intermediate municipalities such as Wijchen.
-
B.
Lelystad–Enkhuizen route
The Lelystad–Enkhuizen route is a Dutch transport corridor across the IJsselmeer that links the cities of Lelystad and Enkhuizen via a major causeway.
-
C.
Haarlem–Leiden corridor
The Haarlem–Leiden corridor is a key transport axis in the western Netherlands linking the cities of Haarlem and Leiden through a network of roads and other infrastructure.
-
D.
Leiden–Alphen–Utrecht corridor
The Leiden–Alphen–Utrecht corridor is a Dutch railway line connecting the cities of Leiden, Alphen aan den Rijn, and Utrecht as part of the Randstad region’s regional rail network.
-
E.
Amsterdam–Alkmaar corridor
The Amsterdam–Alkmaar corridor is a major transport axis in the Netherlands linking the Amsterdam metropolitan area with the city of Alkmaar through a network of roads and other infrastructure.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f7d034819092ecf9682e549c9a |
completed | April 28, 2026, 9:43 p.m. |
Created at: April 16, 2026, 8:33 p.m.