Triple
T21895969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manitoba Hydro |
E540679
|
entity |
| Predicate | hasPowerStationType |
P21222
|
FINISHED |
| Object | hydroelectric generating station |
—
|
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: hydroelectric generating station | Statement: [Manitoba Hydro, hasPowerStationType, hydroelectric generating station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerStationType Context triple: [Manitoba Hydro, hasPowerStationType, hydroelectric generating station]
-
A.
powerplantType
chosen
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
hasPowerHouse
Indicates that one entity possesses or contains a primary energy-producing or central operational unit (a "power house") associated with it.
-
C.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
D.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
E.
powerplantTypeTested
Indicates that a specific type of power plant has been subjected to testing or evaluation.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc700c08190a470fe1ad76c8509 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.