Triple
T15897302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aarlanderveen |
E385491
|
entity |
| Predicate | locatedInPolderArea |
P103735
|
FINISHED |
| Object | Aarlanderveen polder |
—
|
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: Aarlanderveen polder | Statement: [Aarlanderveen, locatedInPolderArea, Aarlanderveen polder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPolderArea Context triple: [Aarlanderveen, locatedInPolderArea, Aarlanderveen polder]
-
A.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
B.
isLocatedInSubdivision
chosen
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
-
C.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
D.
locatedInRiverPlain
Indicates that something is situated within the flat, low-lying area formed by a river’s floodplain.
-
E.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.