Triple
T11813029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht–’s‑Hertogenbosch railway |
E280921
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Houten |
E660008
|
NE FINISHED |
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: Houten | Statement: [Utrecht–’s‑Hertogenbosch railway, servesCity, Houten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Houten Context triple: [Utrecht–’s‑Hertogenbosch railway, servesCity, Houten]
-
A.
Houten
chosen
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.
-
B.
Oosterhout
Oosterhout is a town and municipality in the southern Netherlands known for its historic monasteries and proximity to the city of Breda.
-
C.
Voorhout
Voorhout is a village in South Holland, Netherlands, that forms part of the municipality of Teylingen.
-
D.
Oisterwijk
Oisterwijk is a town in the Dutch province of North Brabant known for its historic center and surrounding forest and fen landscapes.
-
E.
Hoofddorp
Hoofddorp is the main town and administrative center of the municipality of Haarlemmermeer in the Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5cba708819097467bb7aca7fc65 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170d8c9f0819099a398814f49f0ed |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 8, 2026, 9:42 p.m.