Triple

T5448590
Position Surface form Disambiguated ID Type / Status
Subject MOSE flood barrier system E122310 entity
Predicate designedFloodLevel P64371 FINISHED
Object up to 3 metres above normal sea level 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: up to 3 metres above normal sea level | Statement: [MOSE flood barrier system, designedFloodLevel, up to 3 metres above normal sea level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedFloodLevel
Context triple: [MOSE flood barrier system, designedFloodLevel, up to 3 metres above normal sea level]
  • A. designedFloodDischarge
    Indicates the planned or specified amount of water flow that a structure or system is engineered to safely discharge during flood conditions.
  • B. floodResistanceDesign
    Indicates that something is designed or engineered to withstand, mitigate, or remain functional during flooding conditions.
  • C. floodGauge
    Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
  • D. waterLevelRise
    Indicates that the level of water in a given area or container has increased over time.
  • E. hasFloodRisk
    Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
  • 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_69bd4640f52c81909e653ec361f66d76 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd95be329c81908783420cf81b6af5 completed March 20, 2026, 6:45 p.m.
PD Predicate disambiguation batch_69bd919e8d18819098c4af6a015e5cc2 completed March 20, 2026, 6:27 p.m.
PDg Predicate description generation batch_69bd95bd53f48190a03144beb290f2cb completed March 20, 2026, 6:45 p.m.
Created at: March 20, 2026, 2:07 p.m.