Triple
T20315272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofgem |
E510363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government regulator |
C1181
|
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: government regulator Context triple: [Ofgem, instanceOf, government regulator]
-
A.
regulatory authority
chosen
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.
-
B.
government oversight agency
A government oversight agency is an official body responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards within public or private sector activities to ensure accountability and integrity.
-
C.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
D.
government regulatory program
A government regulatory program is an organized set of rules, procedures, and enforcement mechanisms established by a public authority to oversee, control, or guide specific activities or sectors in order to achieve defined policy objectives and protect the public interest.
-
E.
regulatory agency component
A regulatory agency component is a modular part of a regulatory body responsible for performing specific oversight, rulemaking, enforcement, or compliance functions within a defined domain.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:19 a.m.