Triple
T24560473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogun Dam |
E607636
|
entity |
| Predicate | designedInstalledCapacity |
P11312
|
FINISHED |
| Object | 3600 MW |
—
|
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: 3600 MW | Statement: [Rogun Dam, designedInstalledCapacity, 3600 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedInstalledCapacity Context triple: [Rogun Dam, designedInstalledCapacity, 3600 MW]
-
A.
plannedCapacityMW
Indicates the intended or scheduled power generation capacity of an energy asset, measured in megawatts (MW).
-
B.
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.
-
C.
installedCapacityUnit
Indicates the unit of measurement used to express the installed capacity associated with an entity.
-
D.
turbineCapacity
Indicates the power-generating capacity or rated output of a turbine.
-
E.
netElectricalCapacity_MWe
Indicates the relationship specifying an entity’s net electrical power generation capacity, measured in megawatts electric (MWe), after accounting for internal power consumption.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f57a7c8190a0eb8d6d6ef6ae61 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.