Triple
T23132709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cle Elum Lake |
E577217
|
entity |
| Predicate | waterStorageCapacity |
P13057
|
FINISHED |
| Object | approximately 436000 acre-feet |
—
|
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: approximately 436000 acre-feet | Statement: [Cle Elum Lake, waterStorageCapacity, approximately 436000 acre-feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterStorageCapacity Context triple: [Cle Elum Lake, waterStorageCapacity, approximately 436000 acre-feet]
-
A.
waterStorageOrgan
Indicates that one entity functions as an organ specialized for storing water for another entity.
-
B.
waterVolume
chosen
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
C.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
D.
reservoirTotalCapacity
Indicates the maximum volume of water that a reservoir is designed to hold when full.
-
E.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e88909881908c695cd7d39d380c |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.