Triple
T26835902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newfoundland Power |
E675629
|
entity |
| Predicate | obtainsPowerFrom |
P61281
|
FINISHED |
| Object | Newfoundland and Labrador Hydro |
—
|
NE NERFINISHED |
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: Newfoundland and Labrador Hydro | Statement: [Newfoundland Power, obtainsPowerFrom, Newfoundland and Labrador Hydro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obtainsPowerFrom Context triple: [Newfoundland Power, obtainsPowerFrom, Newfoundland and Labrador Hydro]
-
A.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
B.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
C.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
D.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b42ed0c8190b60704546086ec13 |
completed | May 2, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:04 a.m.