Triple
T3056917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Utrecht |
E60503
|
entity |
| Predicate | containsAdministrativeTerritorialEntity |
P747
|
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: [Province of Utrecht, containsAdministrativeTerritorialEntity, Houten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Houten Context triple: [Province of Utrecht, containsAdministrativeTerritorialEntity, 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.
Hoofddorp
Hoofddorp is the main town and administrative center of the municipality of Haarlemmermeer in the Netherlands.
-
E.
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.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e13f16c81909e11ed1444c71151 |
completed | March 8, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c97ca3d5e0819097e904184202b75f |
completed | March 29, 2026, 7:25 p.m. |
Created at: March 8, 2026, 3:02 p.m.