Triple
T10071896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voorne-Putten |
E213647
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Vierpolders |
E118492
|
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: Vierpolders | Statement: [Voorne-Putten, hasTown, Vierpolders]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vierpolders Context triple: [Voorne-Putten, hasTown, Vierpolders]
-
A.
Vierpolders
chosen
Vierpolders is a village in the Dutch province of South Holland, known for its rural character and location near the town of Brielle.
-
B.
Vrouwenpolder
Vrouwenpolder is a coastal village in the Dutch province of Zeeland, known for its wide beaches and location between the North Sea and the Veerse Meer.
-
C.
’s-Gravenpolder
’s-Gravenpolder is a village in the Dutch province of Zeeland, located within the municipality of Borsele.
-
D.
Molenwaard
Molenwaard was a former municipality in the Dutch province of South Holland that later became part of the newly formed municipality of Molenlanden.
-
E.
Molenlanden
Molenlanden is a municipality in the Dutch province of South Holland, known for its rural landscape, historic villages, and proximity to the Kinderdijk windmills.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd01279388190b94c8def00425c78 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29aaa61308190b134b49a6c1c1131 |
completed | April 5, 2026, 5:23 p.m. |
Created at: March 30, 2026, 8:59 p.m.