Triple
T22153679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compagnie Parisienne de Distribution d'Électricité |
E547477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electricity distribution 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 distribution company Context triple: [Compagnie Parisienne de Distribution d'Électricité, instanceOf, electricity distribution 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.
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.
-
C.
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.
-
D.
utilities company
A utilities company is an organization that provides essential public services such as electricity, gas, water, or telecommunications to residential, commercial, and industrial customers, typically under government regulation.
-
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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:33 p.m.