Triple
T33007165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIIO price control |
E844533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ofgem price control |
C51907
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ofgem price control Context triple: [RIIO price control, instanceOf, Ofgem price control]
-
A.
energy supplier
An energy supplier is an entity that procures, manages, and delivers electricity and/or gas to consumers, handling contracts, billing, and customer service while interfacing with energy producers and grid operators.
-
B.
electricity supply industry
The electricity supply industry encompasses the generation, transmission, distribution, and retail of electrical power from producers to end users, ensuring reliable and efficient energy delivery.
-
C.
Electricity regulatory commission
chosen
An electricity regulatory commission is a governing body that oversees, regulates, and enforces policies for the generation, transmission, distribution, and pricing of electrical power to ensure reliability, fairness, and consumer protection.
-
D.
economic regulation
Economic regulation is the set of laws, rules, and administrative actions through which governments influence, control, or guide economic activity, markets, and business behavior to achieve public policy objectives.
-
E.
electricity market
An electricity market is a system in which electricity is traded as a commodity through competitive buying and selling, balancing supply and demand in real time while determining prices for generation, transmission, and consumption.
- F. None of above.
Provenance (1 batch)
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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.