Triple
T303307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoover Dam |
E6243
|
entity |
| Predicate | reservoirCapacity |
P1931
|
FINISHED |
| Object | about 28.9 million 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: about 28.9 million acre-feet | Statement: [Hoover Dam, reservoirCapacity, about 28.9 million acre-feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirCapacity Context triple: [Hoover Dam, reservoirCapacity, about 28.9 million acre-feet]
-
A.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
B.
drainageBasinArea
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
C.
drainageBasin
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
D.
typicalCapacity
chosen
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93c367881908d3f6e2b81d44d7f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.