Triple
T4754086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormvloedkering Hollandse IJssel |
E105544
|
entity |
| Predicate | floodRiskCategory |
P58564
|
FINISHED |
| Object | primary flood defence |
—
|
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: primary flood defence | Statement: [Stormvloedkering Hollandse IJssel, floodRiskCategory, primary flood defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodRiskCategory Context triple: [Stormvloedkering Hollandse IJssel, floodRiskCategory, primary flood defence]
-
A.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
B.
floodConsequence
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
C.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
D.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
E.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
- F. None of above. chosen
Provenance (4 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e72d1c81908eb60960751e52b1 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6424a1d08190ac1d5fc574dc1b55 |
completed | March 20, 2026, 3:13 p.m. |
Created at: March 20, 2026, 1:20 p.m.