Triple
T2126691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Service Electric and Gas Company |
E46441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulated utility |
C5072
|
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: regulated utility Context triple: [Public Service Electric and Gas Company, instanceOf, regulated utility]
-
A.
public utility company
chosen
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
An electric utility is an organization that generates, transmits, and distributes electrical power to consumers while managing infrastructure, reliability, and regulatory compliance.
-
C.
natural gas utility
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.
-
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.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:44 p.m.