Triple
T20725629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waalwijk |
E509426
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Vrijhoeve-Capelle |
—
|
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: Vrijhoeve-Capelle | Statement: [Waalwijk, hasSettlement, Vrijhoeve-Capelle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vrijhoeve-Capelle Context triple: [Waalwijk, hasSettlement, Vrijhoeve-Capelle]
-
A.
Capelle aan den IJssel
Capelle aan den IJssel is a suburban city in the western Netherlands, located just east of Rotterdam along the river IJssel.
-
B.
Capelle
chosen
Capelle is a small village in the Dutch municipality of Waalwijk in the province of North Brabant, Netherlands.
-
C.
Vollenhove
Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
-
D.
Zevenhoven
Zevenhoven is a village in the Dutch province of South Holland, located within the municipality of Nieuwkoop.
-
E.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e7aabc819084f9e9fd45e877fd |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:29 p.m.