Triple
T37314200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Electricity Regulatory Commission |
E926289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory commission |
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: regulatory commission Context triple: [Central Electricity Regulatory Commission, instanceOf, regulatory commission]
-
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.
Electricity regulatory commission
An electricity regulatory commission is a governing body that oversees, regulates, and enforces policies for the generation, transmission, distribution, and pricing of electrical power to ensure reliability, fairness, and consumer protection.
-
C.
securities commission
A securities commission is a government or regulatory authority responsible for overseeing and enforcing laws governing securities markets to protect investors and ensure fair, transparent, and efficient trading.
-
D.
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.
-
E.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.