Triple

T17816136
Position Surface form Disambiguated ID Type / Status
Subject Bergsche Maas E444845 entity
Predicate separationPurpose P129011 FINISHED
Object to reduce flood risk in the Land of Heusden and Altena 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: to reduce flood risk in the Land of Heusden and Altena | Statement: [Bergsche Maas, separationPurpose, to reduce flood risk in the Land of Heusden and Altena]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: separationPurpose
Context triple: [Bergsche Maas, separationPurpose, to reduce flood risk in the Land of Heusden and Altena]
  • A. typeOfSeparation
    Indicates the specific manner or category of separation that exists or occurred between entities.
  • B. separates
    Indicates that one entity divides, parts, or keeps other entities apart from each other.
  • C. separationMethod
    Indicates the technique or process used to separate one substance, component, or entity from another.
  • D. separationProcess
    Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
  • E. definedSeparationFrom
    Indicates a formally specified distinction or boundary established between one entity and another.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4887f7d048190b6d813b9f0fab3e7 completed April 19, 2026, 7:47 a.m.
PD Predicate disambiguation batch_69e3d8de28688190844b65acf6af54e6 completed April 18, 2026, 7:17 p.m.
PDg Predicate description generation batch_69e3db7704588190a34a422421152173 completed April 18, 2026, 7:28 p.m.
Created at: April 10, 2026, 10:14 a.m.