Triple
T13084505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Thompson River |
E310294
|
entity |
| Predicate | floodDate |
P88904
|
FINISHED |
| Object | 31 July 1976 |
—
|
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: 31 July 1976 | Statement: [Big Thompson River, floodDate, 31 July 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodDate Context triple: [Big Thompson River, floodDate, 31 July 1976]
-
A.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
B.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
C.
dateOfMajorDrainageEvent
chosen
Indicates the specific date on which a significant drainage-related event (such as major flooding, diversion, or alteration of water flow) occurred.
-
D.
runoffDate
Indicates the date on which a runoff event (such as a runoff election or runoff water occurrence) takes place or is scheduled.
-
E.
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.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.