Triple
T27708409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HHS to conduct compliance reviews |
E698613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory authority action |
C22261
|
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 authority action Context triple: [HHS to conduct compliance reviews, instanceOf, regulatory authority action]
-
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.
regulatory activity
chosen
Regulatory activity is the process by which an entity establishes, interprets, or enforces rules and standards to guide or control the behavior of systems, organizations, or individuals.
-
C.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
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.
regulatory authorisation
Regulatory authorisation is the formal approval granted by a competent authority that permits an organisation, product, service, or activity to operate in compliance with applicable laws and regulations.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3:01 p.m.