Triple
T35468867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teton Dam failure flooding |
E1025153
|
entity |
| Predicate | warningTimeBeforeFullBreach |
P81572
|
FINISHED |
| Object | a few hours |
—
|
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: a few hours | Statement: [Teton Dam failure flooding, warningTimeBeforeFullBreach, a few hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningTimeBeforeFullBreach Context triple: [Teton Dam failure flooding, warningTimeBeforeFullBreach, a few hours]
-
A.
warningLeadTime
chosen
Indicates the amount of time in advance that a warning is issued before an event or condition occurs.
-
B.
timeThreshold
Indicates a temporal limit or cutoff point after which a related condition, event, or state changes or no longer applies.
-
C.
breachedAt
Indicates the specific time or point at which a security, contract, or boundary was violated or broken.
-
D.
mayBeBreachBy
Indicates that something has the potential to constitute a breach committed by a specified party.
-
E.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
- 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_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.