Triple
T19244667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam–Amersfoort railway |
E481216
|
entity |
| Predicate | connectsWithLine |
P845
|
FINISHED |
| Object | Weesp–Lelystad 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: Weesp–Lelystad railway | Statement: [Amsterdam–Amersfoort railway, connectsWithLine, Weesp–Lelystad railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weesp–Lelystad railway Context triple: [Amsterdam–Amersfoort railway, connectsWithLine, Weesp–Lelystad railway]
-
A.
Zwolle–Lelystad railway
The Zwolle–Lelystad railway is a Dutch rail line connecting the city of Zwolle with Lelystad, forming part of an important north–south route in the Netherlands’ rail network.
-
B.
Weesp–Leiden railway
The Weesp–Leiden railway is a key rail line in the Netherlands connecting the Amsterdam area with Leiden and serving as an important corridor in the Randstad region’s passenger rail network.
-
C.
Woerden–Leiden railway
The Woerden–Leiden railway is a regional rail line in the Netherlands connecting the city of Leiden with Woerden and serving intermediate towns in South Holland and Utrecht.
-
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.
Haarlem–Zandvoort railway
The Haarlem–Zandvoort railway is a short Dutch rail line in North Holland that connects the city of Haarlem with the coastal resort town of Zandvoort, serving as an important route for commuters and beachgoers.
- 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: Weesp–Lelystad railway Target entity description: The Weesp–Lelystad railway is a Dutch rail line in the province of Flevoland that connects the town of Weesp with the city of Lelystad, forming part of the main route between Amsterdam and the northeastern Netherlands.
-
A.
Zwolle–Lelystad railway
The Zwolle–Lelystad railway is a Dutch rail line connecting the city of Zwolle with Lelystad, forming part of an important north–south route in the Netherlands’ rail network.
-
B.
Weesp–Leiden railway
The Weesp–Leiden railway is a key rail line in the Netherlands connecting the Amsterdam area with Leiden and serving as an important corridor in the Randstad region’s passenger rail network.
-
C.
Woerden–Leiden railway
The Woerden–Leiden railway is a regional rail line in the Netherlands connecting the city of Leiden with Woerden and serving intermediate towns in South Holland and Utrecht.
-
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.
Haarlem–Zandvoort railway
The Haarlem–Zandvoort railway is a short Dutch rail line in North Holland that connects the city of Haarlem with the coastal resort town of Zandvoort, serving as an important route for commuters and beachgoers.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf47820819081e8b6af852bb1dd |
completed | April 20, 2026, 10:07 a.m. |
Created at: April 10, 2026, 1:27 p.m.