Triple
T33007163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIIO price control |
E844533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | energy network price control framework |
C58549
|
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: energy network price control framework Context triple: [RIIO price control, instanceOf, energy network price control framework]
-
A.
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.
-
B.
RIIO price control period
chosen
The RIIO price control period is a multi-year regulatory framework used by the UK energy regulator to set allowed revenues and performance incentives for network companies based on outputs, innovation, and efficiency.
-
C.
national grid system
A national grid system is a standardized framework of coordinates and infrastructure used to generate, transmit, and distribute electricity reliably across a country.
-
D.
electricity reliability regulator
An electricity reliability regulator is an authority responsible for setting, monitoring, and enforcing standards to ensure the continuous, safe, and dependable operation of the electric power system.
-
E.
Electricity regulatory commission
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.
- 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.