Triple
T11921367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalubaale Power Station |
E283663
|
entity |
| Predicate | originalInstalledCapacity |
P11312
|
FINISHED |
| Object | 150 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: 150 megawatts | Statement: [Nalubaale Power Station, originalInstalledCapacity, 150 megawatts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalInstalledCapacity Context triple: [Nalubaale Power Station, originalInstalledCapacity, 150 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.
initialHardDriveCapacity
Indicates the original storage capacity of a hard drive at the time it was first provided, installed, or configured.
-
C.
bootCapacity
Indicates the storage volume or carrying capacity available in the boot (trunk) of a vehicle.
-
D.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
E.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e1b08481909ed291667035f330 |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.