Triple
T22621827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuiderwoude |
E558301
|
entity |
| Predicate | locatedInPolderLandscape |
P127806
|
FINISHED |
| Object | Dutch polder landscape |
—
|
LITERAL 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: Dutch polder landscape | Statement: [Zuiderwoude, locatedInPolderLandscape, Dutch polder landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPolderLandscape Context triple: [Zuiderwoude, locatedInPolderLandscape, Dutch polder landscape]
-
A.
containsPolder
Indicates that one geographic or administrative area includes a polder within its boundaries.
-
B.
isInPolderRegion
chosen
Indicates that one entity is located within a polder region, i.e., land reclaimed from a body of water and typically protected by dikes.
-
C.
locatedWithinNationalLandscape
Indicates that one entity is geographically situated inside the boundaries of a designated national landscape area.
-
D.
locatedInRiverPlain
Indicates that something is situated within the flat, low-lying area formed by a river’s floodplain.
-
E.
locatedInNationalCharacterArea
Indicates that one entity is geographically situated within the boundaries of a specified national character area.
- F. None of above.
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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e39959481909e0ae67379435f95 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.