Triple

T34291410
Position Surface form Disambiguated ID Type / Status
Subject Zeeland E879897 entity
Predicate hasStormSurgeBarrier P25048 FINISHED
Object Oosterscheldekering 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: Oosterscheldekering | Statement: [Zeeland, hasStormSurgeBarrier, Oosterscheldekering]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStormSurgeBarrier
Context triple: [Zeeland, hasStormSurgeBarrier, Oosterscheldekering]
  • A. hasBreakwater
    Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
  • B. stormSurge_m
    Indicates a relationship where a storm causes an abnormal rise in sea level, typically leading to coastal flooding.
  • C. hasFloodProtectionInfrastructure chosen
    Indicates that there exists built or implemented infrastructure designed to protect against or mitigate flooding for the referenced entity.
  • D. stormSurgeHeight_feet
    Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
  • E. designedForFloodMitigationOf
    Indicates that something is specifically created or configured to reduce, control, or manage flooding affecting a particular entity or area.
  • 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_69f349b6df1c81908e5e5b6c2ab6409b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff8aff48988190a48a440de8238ef9 completed May 9, 2026, 7:29 p.m.
PD Predicate disambiguation batch_69ff8a780404819082f48ceb21e7fe11 completed May 9, 2026, 7:26 p.m.
Created at: May 1, 2026, 1:57 a.m.