Triple
T8251743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Ethiopian Renaissance Dam |
E192973
|
entity |
| Predicate | claimedInstalledCapacity |
P11312
|
FINISHED |
| Object | 6000 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: 6000 MW | Statement: [Grand Ethiopian Renaissance Dam, claimedInstalledCapacity, 6000 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedInstalledCapacity Context triple: [Grand Ethiopian Renaissance Dam, claimedInstalledCapacity, 6000 MW]
-
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.
bootCapacity
Indicates the storage volume or carrying capacity available in the boot (trunk) of a vehicle.
-
C.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
D.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
capitalClaimed
Indicates that an entity asserts or designates another entity as its capital.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78ca4b0881909bb1fb550dba59e7 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.