Triple
T16582897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walcheren |
E402879
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Vrouwenpolder |
E374629
|
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: Vrouwenpolder | Statement: [Walcheren, contains, Vrouwenpolder]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vrouwenpolder Context triple: [Walcheren, contains, Vrouwenpolder]
-
A.
Vrouwenpolder
chosen
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.
-
B.
Numansdorpse Polder
Numansdorpse Polder is a reclaimed low-lying tract of land in the Netherlands, protected by dikes and used primarily for agriculture near the village of Numansdorp.
-
C.
Ooijpolder
Ooijpolder is a Dutch riverine polder and nature area near Nijmegen, known for its scenic floodplains, wetlands, and rich birdlife along the Waal River.
-
D.
’s-Gravenpolder
’s-Gravenpolder is a village in the Dutch province of Zeeland, located within the municipality of Borsele.
-
E.
Eemnesser Polder
Eemnesser Polder is a low-lying reclaimed polder area in the Netherlands known for its characteristic Dutch landscape of fields, dikes, and waterways.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35999088c8190900497f18728bd0b |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ef2d6048190954144ab848760ec |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:16 a.m.