Triple
T2759160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folsom Dam |
E61177
|
entity |
| Predicate | reservoirMaxCapacity |
P14460
|
FINISHED |
| Object | about 1,000,000 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 1,000,000 acre-feet | Statement: [Folsom Dam, reservoirMaxCapacity, about 1,000,000 acre-feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirMaxCapacity Context triple: [Folsom Dam, reservoirMaxCapacity, about 1,000,000 acre-feet]
-
A.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
B.
hasMajorReservoir
Indicates that an entity possesses or is associated with a primary or significant reservoir (such as a large storage or accumulation of a resource).
-
C.
majorReservoir
Indicates that one entity functions as a primary or significant water-storage reservoir associated with another entity.
-
D.
reservoirSurfaceArea
Indicates the total area covered by the surface of a reservoir.
-
E.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb8d34f88190a760111fe303cf24 |
completed | March 7, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69abd82de7f48190acd614f28644c6da |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:57 p.m.