Triple
T35468866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teton Dam failure flooding |
E1025153
|
entity |
| Predicate | reservoirFillingStart |
P39983
|
FINISHED |
| Object | late 1975 |
—
|
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: late 1975 | Statement: [Teton Dam failure flooding, reservoirFillingStart, late 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirFillingStart Context triple: [Teton Dam failure flooding, reservoirFillingStart, late 1975]
-
A.
constructionStartOfReservoir
Indicates that the referenced event or time marks the beginning of construction work on a reservoir.
-
B.
reservoirCreated
chosen
Indicates that a reservoir has been brought into existence, typically through construction or formation by some agent or process.
-
C.
reservoirCreatedFor
Indicates that a reservoir was constructed or designated to serve a particular purpose, use, or beneficiary.
-
D.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
-
E.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.