Triple
T4611751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandoh Dam |
E100573
|
entity |
| Predicate | reservoirActiveCapacity |
P48318
|
FINISHED |
| Object | 33,000,000 m3 |
—
|
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: 33,000,000 m3 | Statement: [Pandoh Dam, reservoirActiveCapacity, 33,000,000 m3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirActiveCapacity Context triple: [Pandoh Dam, reservoirActiveCapacity, 33,000,000 m3]
-
A.
reservoirLiveStorageCapacity_m3
chosen
Indicates the volume of water that a reservoir can actively store and use, measured in cubic meters.
-
B.
reservoirTotalCapacity
Indicates the maximum volume of water that a reservoir is designed to hold when full.
-
C.
reservoirGrossStorageCapacity_m3
Indicates the total volume of water a reservoir can hold when filled to its maximum designed storage level, measured in cubic meters.
-
D.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
-
E.
reservoirElevation
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59bffbf08190b13ef0810e6f9d19 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.