Triple
T26559982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Falls Dam |
E666211
|
entity |
| Predicate | managesWaterLevelsOf |
P130170
|
FINISHED |
| Object | Spokane River |
—
|
NE NERFINISHED |
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: Spokane River | Statement: [Post Falls Dam, managesWaterLevelsOf, Spokane River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesWaterLevelsOf Context triple: [Post Falls Dam, managesWaterLevelsOf, Spokane River]
-
A.
controlsWaterLevelOf
chosen
Indicates that one entity has the ability or authority to regulate or adjust the water level of another entity or system.
-
B.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
C.
managesReservoir
Indicates that one entity is responsible for overseeing, operating, and controlling the use or condition of a reservoir.
-
D.
typeOfWaterManaged
Indicates the specific kind or category of water that is overseen, controlled, or handled within a management context.
-
E.
hasWaterManagementStructure
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 1:52 a.m.