Triple
T18133480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Delta Works region |
E434074
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Volkerakdam |
—
|
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: Volkerakdam | Statement: [Dutch Delta Works region, contains, Volkerakdam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Volkerakdam Context triple: [Dutch Delta Works region, contains, Volkerakdam]
-
A.
Volkerakdam
chosen
Volkerakdam is a major Dutch dam and water management structure that forms part of the Delta Works system, helping to control water levels and protect against flooding in the Rhine–Meuse–Scheldt delta.
-
B.
Volkeraksluizen
Volkeraksluizen is a major lock complex in the Netherlands that regulates water levels and shipping traffic between the Volkerak and surrounding waterways.
-
C.
Amerongen weir
Amerongen weir is a major hydraulic structure on the Nederrijn in the Netherlands that regulates river water levels and flow through a system of floodgates.
-
D.
Diemel Dam
Diemel Dam is a German reservoir dam that was one of the targets attacked during the World War II Dambusters Raid.
-
E.
Daan Dam
Daan Dam is the child of renowned Dutch architect Cees Dam.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de04321c81909c0b9d47757720fd |
completed | April 19, 2026, 1:52 p.m. |
Created at: April 10, 2026, 10:29 a.m.