Triple
T17614817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanapum Dam |
E429055
|
entity |
| Predicate | regulatesRiverFlow |
P109423
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wanapum Dam, regulatesRiverFlow, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesRiverFlow Context triple: [Wanapum Dam, regulatesRiverFlow, yes]
-
A.
riverRegulation
chosen
Indicates the management or control of a river’s flow, level, or course through human interventions such as dams, channels, or other regulatory measures.
-
B.
watercourseControlled
Indicates that one entity exercises control, regulation, or management over a watercourse (such as a river, stream, or canal).
-
C.
riverManaged
Indicates that a river is subject to management, regulation, or oversight by a particular authority, organization, or system.
-
D.
regulatesFlowFor
Indicates that one entity controls, directs, or manages the rate or movement of another entity’s flow.
-
E.
regulatesReservoir
Indicates that one entity controls, manages, or influences the operation, levels, or behavior of a reservoir.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3174008190a2b5bb1b061ea4df |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.