Triple

T1468755
Position Surface form Disambiguated ID Type / Status
Subject Hollandsche IJssel E27084 entity
Predicate hasFloodDefenseFunction P25048 FINISHED
Object protection of Randstad against high river levels 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: protection of Randstad against high river levels | Statement: [Hollandsche IJssel, hasFloodDefenseFunction, protection of Randstad against high river levels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFloodDefenseFunction
Context triple: [Hollandsche IJssel, hasFloodDefenseFunction, protection of Randstad against high river levels]
  • A. hasFloodProtectionInfrastructure chosen
    Indicates that there exists built or implemented infrastructure designed to protect against or mitigate flooding for the referenced entity.
  • B. hasFloodRisk
    Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
  • C. hasFloodProtectionProject
    Indicates that a flood protection project exists or is implemented for the referenced entity.
  • D. hasFloodplain
    Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
  • E. hasSeasonalFlooding
    Indicates that an area regularly experiences flooding during specific, recurring times of the year.
  • 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_69a496d25d6881909dbd84f86d763992 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c5d8bb68819095b7b413247ad657 completed March 1, 2026, 11:03 p.m.
PD Predicate disambiguation batch_69a4c48350d88190a81bd149103f93e3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:01 p.m.