Triple
T15696001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelstoke Dam |
E380460
|
entity |
| Predicate | initialInstalledCapacity |
P28148
|
FINISHED |
| Object | 1843 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: 1843 MW | Statement: [Revelstoke Dam, initialInstalledCapacity, 1843 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialInstalledCapacity Context triple: [Revelstoke Dam, initialInstalledCapacity, 1843 MW]
-
A.
installedCapacity
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.
originalCapacity
chosen
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
E.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.