Triple
T4068781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Company |
E86592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gas utility holding company |
C1393
|
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: gas utility holding company Context triple: [Southern Company, instanceOf, gas utility holding 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.
natural gas utility
chosen
A natural gas utility is a regulated service provider that supplies, transports, and distributes natural gas to residential, commercial, and industrial customers through an integrated pipeline infrastructure.
-
C.
electric utility
An electric utility is an organization that generates, transmits, and distributes electrical power to consumers while managing infrastructure, reliability, and regulatory compliance.
-
D.
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.
-
E.
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.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.