Triple
T14227306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZESCO |
E352655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electricity utility company |
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 utility company Context triple: [ZESCO, instanceOf, electricity utility company]
-
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.
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.
-
C.
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.
-
D.
electricity industry association
An electricity industry association is an organized group that represents and advocates for the collective interests of companies and stakeholders involved in the generation, transmission, distribution, and sale of electric power.
-
E.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:07 a.m.