Triple
T22304331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Municipal Utility District |
E551335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-owned 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: community-owned utility Context triple: [Sacramento Municipal Utility District, instanceOf, community-owned utility]
-
A.
community energy project
A community energy project is a locally initiated and collectively governed initiative that develops, owns, or manages energy generation, efficiency, or storage systems to meet shared social, environmental, and economic goals.
-
B.
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.
-
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.
investor-owned utility company
An investor-owned utility company is a privately owned, profit-driven enterprise that provides essential public services such as electricity, gas, or water to customers under government regulation.
-
E.
consumer cooperative
A consumer cooperative is a business owned and democratically controlled by the customers who use its goods or services, operating primarily to meet their needs rather than to maximize profit.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.