Triple
T12028958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OIRA |
E286352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory review body |
C17920
|
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 review body Context triple: [OIRA, instanceOf, regulatory review body]
-
A.
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.
-
B.
federal oversight body
chosen
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.
-
C.
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.
-
D.
pharmacovigilance body
A pharmacovigilance body is an organization responsible for monitoring, assessing, and preventing adverse effects or other drug-related problems to ensure the ongoing safety and effective use of medicines.
-
E.
government agency oversight body
A government agency oversight body is an independent or semi-independent entity responsible for monitoring, evaluating, and ensuring that government agencies operate legally, ethically, efficiently, and in alignment with established policies and public interests.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.