Triple

T12495980
Position Surface form Disambiguated ID Type / Status
Subject Muddy River Restoration Project E298684 entity
Predicate typeOfFloodControl P42410 FINISHED
Object stormwater flood mitigation 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: stormwater flood mitigation | Statement: [Muddy River Restoration Project, typeOfFloodControl, stormwater flood mitigation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfFloodControl
Context triple: [Muddy River Restoration Project, typeOfFloodControl, stormwater flood mitigation]
  • A. riverControl
    Indicates a relationship where one entity manages, regulates, or exerts authority over the flow, usage, or conditions of a river.
  • B. floodGauge
    Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
  • C. providesFloodControlFor chosen
    Indicates that one entity offers protection or mitigation against flooding for another entity or area.
  • D. floodStage
    Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
  • E. flowControl
    Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
  • 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_69d6ada4cd388190ae3bbf83ff87057a completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94e8a706c8190873623eab7db607d completed April 10, 2026, 7:24 p.m.
PD Predicate disambiguation batch_69d94d41f3cc8190a3331fb9a895306f completed April 10, 2026, 7:19 p.m.
Created at: April 8, 2026, 9:57 p.m.