Triple
T32037224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRC Office of Enforcement |
E818127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office of a federal agency |
C57166
|
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: office of a federal agency Context triple: [NRC Office of Enforcement, instanceOf, office of a federal agency]
-
A.
office of the United States government
An office of the United States government is an official organizational unit or position within a federal branch or agency that carries out specific governmental functions, duties, and responsibilities under U.S. law.
-
B.
federal government legal office
A federal government legal office is an organizational unit within a national government that provides legal advice, representation, and regulatory support to federal agencies and officials in carrying out their statutory and constitutional responsibilities.
-
C.
Federal agency
chosen
A federal agency is a government organization established by national law to implement, administer, and enforce specific public policies and programs at the federal level.
-
D.
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.
-
E.
bureaucratic agency
A bureaucratic agency is a formal organizational entity within a government or large institution that implements policies and regulations through standardized procedures, hierarchical authority, and specialized administrative roles.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.