Triple
T9380866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OVO Energy |
E225777
|
entity |
| Predicate | energySourceFocus |
P5332
|
FINISHED |
| Object | renewable electricity |
—
|
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: renewable electricity | Statement: [OVO Energy, energySourceFocus, renewable electricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySourceFocus Context triple: [OVO Energy, energySourceFocus, renewable electricity]
-
A.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
B.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
-
C.
energyAspect
Indicates a relationship where one entity represents an aspect, component, or characteristic related to the energy properties or behavior of another entity.
-
D.
energyStrategy
Indicates a relationship where an entity adopts, follows, or is characterized by a particular plan or approach for producing, managing, or using energy.
-
E.
energyContext
Indicates the situational or environmental conditions under which energy is produced, used, transferred, or transformed in relation to the entities involved.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bc94108190a1b8146a78166009 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.