Triple
T3849379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center for Drug Evaluation and Research |
E85252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory agency division |
C1024
|
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 agency division Context triple: [Center for Drug Evaluation and Research, instanceOf, regulatory agency division]
-
A.
government agency division
chosen
A government agency division is a specialized organizational unit within a larger government agency that focuses on a specific set of functions, programs, or policy areas to support the agency’s overall mission.
-
B.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
C.
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.
-
D.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
E.
executive branch agency
An executive branch agency is a governmental organization within the executive branch responsible for implementing, administering, and enforcing laws and public policies under the direction of the chief executive.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.