Triple
T14232436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eindhoven–Breda railway |
E352783
|
entity |
| Predicate | connectsVia |
P845
|
FINISHED |
| Object | Oisterwijk |
—
|
NE NERFINISHED |
How this triple was built (2 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: Oisterwijk | Statement: [Eindhoven–Breda railway, connectsVia, Oisterwijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oisterwijk Context triple: [Eindhoven–Breda railway, connectsVia, Oisterwijk]
-
A.
Oisterwijk
chosen
Oisterwijk is a town in the Dutch province of North Brabant known for its historic center and surrounding forest and fen landscapes.
-
B.
Zoeterwoude
Zoeterwoude is a small Dutch municipality and village known for its rural character and location near Leiden in the province of South Holland.
-
C.
Houten
Houten is a Dutch town in the province of Utrecht, known for its bicycle-friendly urban design and as the home of the Royal Dutch Mint.
-
D.
Weesp
Weesp is a historic town in the province of North Holland in the Netherlands, known for its canals, fortified structures, and traditional Dutch architecture.
-
E.
Oosterhout
Oosterhout is a town and municipality in the southern Netherlands known for its historic monasteries and proximity to the city of Breda.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
Created at: April 10, 2026, 1:07 a.m.