Triple
T14490305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Council of Himachal Pradesh |
E359342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regulatory body |
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 body Context triple: [Bar Council of Himachal Pradesh, instanceOf, Regulatory body]
-
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.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
C.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
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.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.