Triple
T1270951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeslantkering |
E15706
|
entity |
| Predicate | designedForWaterLevel |
P20750
|
FINISHED |
| Object | 3.0 m above NAP |
—
|
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: 3.0 m above NAP | Statement: [Maeslantkering, designedForWaterLevel, 3.0 m above NAP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForWaterLevel Context triple: [Maeslantkering, designedForWaterLevel, 3.0 m above NAP]
-
A.
minimumWaterDepthAboveCrest
Indicates the smallest required depth of water that must be maintained above the crest level of a structure or feature.
-
B.
designedToWithstand
chosen
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
C.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
D.
waterColumnZone
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
-
E.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06ae7b88190a1e0b5232d84a7b1 |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.