Triple
T9302074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easyEnergy |
E223788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | energy supply company |
C15080
|
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 supply company Context triple: [easyEnergy, instanceOf, energy supply company]
-
A.
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.
-
B.
wholesale energy company
A wholesale energy company is a business that buys large quantities of electricity or fuel from producers and sells them in bulk to utilities, large industrial customers, or other resellers, often managing supply, pricing, and risk in energy markets.
-
C.
energy solutions company
chosen
An energy solutions company designs, develops, and delivers technologies and services that provide efficient, reliable, and sustainable energy to residential, commercial, and industrial customers.
-
D.
integrated energy company
An integrated energy company is a business that operates across multiple stages of the energy value chain—such as exploration, production, refining, distribution, and retail—often spanning both fossil fuels and renewable energy sources.
-
E.
electric utility
An electric utility is an organization that generates, transmits, and distributes electrical power to consumers while managing infrastructure, reliability, and regulatory compliance.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.