Triple
T23077880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Public Service Commissioner |
E575380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public utility regulator |
C12723
|
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: public utility regulator Context triple: [Louisiana Public Service Commissioner, instanceOf, public utility regulator]
-
A.
utility division
A utility division is an organizational unit within a company responsible for managing and delivering essential support services—such as power, water, communications, or shared infrastructure—to internal or external customers efficiently and reliably.
-
B.
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.
-
C.
utility mob
A utility mob is a non-player entity designed primarily to provide functional benefits—such as resources, services, or environmental effects—rather than direct combat or narrative roles.
-
D.
public utilities commission
chosen
A public utilities commission is a government regulatory body that oversees and sets standards, rates, and practices for essential public services such as electricity, gas, water, and telecommunications to protect consumers and ensure reliable, fair service.
-
E.
engineering regulator
An engineering regulator is an entity or mechanism that establishes, enforces, and monitors technical standards, safety requirements, and compliance within engineering practices and systems.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.