Triple

T19390198
Position Surface form Disambiguated ID Type / Status
Subject 2009 Red River flood E485044 entity
Predicate floodStageExceededDuration P81975 FINISHED
Object several weeks in some locations 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: several weeks in some locations | Statement: [2009 Red River flood, floodStageExceededDuration, several weeks in some locations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: floodStageExceededDuration
Context triple: [2009 Red River flood, floodStageExceededDuration, several weeks in some locations]
  • A. floodStage chosen
    Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
  • 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. floodPeakDischarge
    Indicates the maximum rate of water flow occurring at the peak of a flood event in a river or channel.
  • D. floodEvent
    Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
  • E. floodRecord
    Indicates that an entity serves as a documented record or report of a flood event affecting another 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61b4328448190b6347c41265e820c completed April 20, 2026, 12:25 p.m.
PD Predicate disambiguation batch_69e4fd602f008190aa9bc76ae17e4ce1 completed April 19, 2026, 4:05 p.m.
Created at: April 10, 2026, 1:36 p.m.