Triple
T15027159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celilo Falls |
E378246
|
entity |
| Predicate | inundatedBy |
P42186
|
FINISHED |
| Object | filling of Lake Celilo |
—
|
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: filling of Lake Celilo | Statement: [Celilo Falls, inundatedBy, filling of Lake Celilo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inundatedBy Context triple: [Celilo Falls, inundatedBy, filling of Lake Celilo]
-
A.
submergedBy
chosen
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
B.
formedBySubmerging
Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
-
C.
bombardedBy
Indicates that an entity is subjected to an intense or repeated attack, impact, or influx from another entity.
-
D.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
E.
impactedRiver
Indicates that one entity has caused a significant effect, alteration, or disturbance to a river or its conditions.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7dfcb508190aec8cd667e27a8ea |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:58 a.m.