Triple
T38266609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Big Thompson Canyon flood |
E1021078
|
entity |
| Predicate | floodHeight |
P190226
|
FINISHED |
| Object | up to about 20 feet in places |
—
|
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 about 20 feet in places | Statement: [1976 Big Thompson Canyon flood, floodHeight, up to about 20 feet in places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodHeight Context triple: [1976 Big Thompson Canyon flood, floodHeight, up to about 20 feet in places]
-
A.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
B.
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.
-
C.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc330b4288190858b49d986160706 |
completed | May 7, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.