Triple
T23471715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kajaki Dam |
E570146
|
entity |
| Predicate | totalOriginalInstalledCapacity |
P11312
|
FINISHED |
| Object | 33 megawatts |
—
|
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 megawatts | Statement: [Kajaki Dam, totalOriginalInstalledCapacity, 33 megawatts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalOriginalInstalledCapacity Context triple: [Kajaki Dam, totalOriginalInstalledCapacity, 33 megawatts]
-
A.
installedCapacity
chosen
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
B.
installedCapacityUnit
Indicates the unit of measurement used to express the installed capacity associated with an entity.
-
C.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
-
D.
initialHardDriveCapacity
Indicates the original storage capacity of a hard drive at the time it was first provided, installed, or configured.
-
E.
formerCapacityUse
Indicates that an entity previously held or used a particular role, function, or capacity, but no longer does so.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a700bd0481908047aa4678217cbd |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:55 p.m.