Triple
T22815830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilburg railway station |
E565094
|
entity |
| Predicate | isOnRoute |
P2127
|
FINISHED |
| Object | Utrecht–Tilburg–Breda intercity 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: Utrecht–Tilburg–Breda intercity route | Statement: [Tilburg railway station, isOnRoute, Utrecht–Tilburg–Breda intercity route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Utrecht–Tilburg–Breda intercity route Context triple: [Tilburg railway station, isOnRoute, Utrecht–Tilburg–Breda intercity route]
-
A.
Amsterdam–Eindhoven railway corridor
The Amsterdam–Eindhoven railway corridor is a major Dutch rail axis connecting the capital Amsterdam with the southern city of Eindhoven, serving as a key route for both intercity and regional train services.
-
B.
Eindhoven–Tilburg rail corridor
The Eindhoven–Tilburg rail corridor is a key railway line in the southern Netherlands that connects the cities of Eindhoven and Tilburg and serves as an important regional and intercity passenger route.
-
C.
Utrecht–Hilversum–Amersfoort railway
The Utrecht–Hilversum–Amersfoort railway is a key Dutch rail route connecting the central hub of Utrecht with the cities of Hilversum and Amersfoort in the central Netherlands.
-
D.
Tilburg–Nijmegen railway
The Tilburg–Nijmegen railway is a Dutch rail line in the southern Netherlands that connects the cities of Tilburg and Nijmegen via intermediate towns such as Oss.
-
E.
Breda–Tilburg railway line
The Breda–Tilburg railway line is a Dutch rail route in the province of North Brabant that connects the cities of Breda and Tilburg and serves intermediate towns such as Gilze en Rijen.
- 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: Utrecht–Tilburg–Breda intercity route Target entity description: The Utrecht–Tilburg–Breda intercity route is a Dutch long-distance passenger rail service connecting the central city of Utrecht with the southern cities of Tilburg and Breda.
-
A.
Amsterdam–Eindhoven railway corridor
The Amsterdam–Eindhoven railway corridor is a major Dutch rail axis connecting the capital Amsterdam with the southern city of Eindhoven, serving as a key route for both intercity and regional train services.
-
B.
Eindhoven–Tilburg rail corridor
The Eindhoven–Tilburg rail corridor is a key railway line in the southern Netherlands that connects the cities of Eindhoven and Tilburg and serves as an important regional and intercity passenger route.
-
C.
Utrecht–Hilversum–Amersfoort railway
The Utrecht–Hilversum–Amersfoort railway is a key Dutch rail route connecting the central hub of Utrecht with the cities of Hilversum and Amersfoort in the central Netherlands.
-
D.
Tilburg–Nijmegen railway
The Tilburg–Nijmegen railway is a Dutch rail line in the southern Netherlands that connects the cities of Tilburg and Nijmegen via intermediate towns such as Oss.
-
E.
Breda–Tilburg railway line
The Breda–Tilburg railway line is a Dutch rail route in the province of North Brabant that connects the cities of Breda and Tilburg and serves intermediate towns such as Gilze en Rijen.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcc41ac81908167856be021ea24 |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:33 p.m.