Triple
T4103272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Regulatory Affairs |
E88389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal field organization |
C14329
|
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: federal field organization Context triple: [Office of Regulatory Affairs, instanceOf, federal field organization]
-
A.
field operating agency
chosen
A field operating agency is an organizational unit that performs specialized, mission-support or operational functions for a higher headquarters, typically operating outside the main administrative structure and often dispersed geographically.
-
B.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
C.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
-
D.
federal unit
A federal unit is a constituent political entity, such as a state or province, within a federal system that shares sovereignty with a central government while retaining certain autonomous powers.
-
E.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.