Triple
T9380874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OVO Energy |
E225777
|
entity |
| Predicate | acquisitionOfSSEEnergyServices |
P88623
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [OVO Energy, acquisitionOfSSEEnergyServices, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfSSEEnergyServices Context triple: [OVO Energy, acquisitionOfSSEEnergyServices, 2020]
-
A.
energyCooperation
Indicates a collaborative relationship in which entities work together to share, develop, or manage energy resources, technologies, or policies.
-
B.
energyTitleAdministeredBy
Indicates that the authority or responsibility for administering an energy-related title is held by a specified agent or organization.
-
C.
hasEnergyTransition
Indicates a change in an entity’s primary energy source, technology, or system from one form or configuration to another over time.
-
D.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
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. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.