Triple
T28138789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Midlands Electricity Board |
E714284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electricity board |
C359
|
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: electricity board Context triple: [East Midlands Electricity Board, instanceOf, electricity board]
-
A.
electric utility
chosen
An electric utility is an organization that generates, transmits, and distributes electrical power to consumers while managing infrastructure, reliability, and regulatory compliance.
-
B.
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.
-
C.
public utility company
A public utility company is an organization, often government-regulated, that provides essential services such as electricity, water, gas, or telecommunications to the public, typically operating as a natural monopoly to ensure reliable and widespread access.
-
D.
utility management company
A utility management company is an organization that oversees, optimizes, and administers essential services such as electricity, water, gas, and waste for residential, commercial, or industrial clients.
-
E.
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.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 9:51 p.m.