Triple
T23471714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kajaki Dam |
E570146
|
entity |
| Predicate | originalTurbineCapacity |
P30472
|
FINISHED |
| Object | 16.5 megawatts each |
—
|
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: 16.5 megawatts each | Statement: [Kajaki Dam, originalTurbineCapacity, 16.5 megawatts each]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTurbineCapacity Context triple: [Kajaki Dam, originalTurbineCapacity, 16.5 megawatts each]
-
A.
turbineCapacity
chosen
Indicates the power-generating capacity or rated output of a turbine.
-
B.
totalElectricalCapacity_MWe
Indicates the total electrical power generation capacity, measured in megawatts electric (MWe), that an entity can produce or supply.
-
C.
grossElectricalCapacity_MWe
Indicates the total electrical power output capacity of a generating unit, measured in megawatts electric (MWe), before accounting for internal power consumption or losses.
-
D.
turbineType
Indicates the specific kind or category of turbine associated with or used by an entity.
-
E.
typicalTurbineType
Indicates the turbine type that is most commonly or characteristically used or found in association with a given entity or context.
- 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.