Triple
T338238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanford Federal Facility Agreement and Consent Order |
E6775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal facility compliance agreement |
C3151
|
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 facility compliance agreement Context triple: [Hanford Federal Facility Agreement and Consent Order, instanceOf, federal facility compliance agreement]
-
A.
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.
-
B.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
C.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
D.
federally owned corporation
A federally owned corporation is a government-established legal entity that operates commercial or public service activities on behalf of the federal government while retaining a distinct corporate structure.
-
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. chosen
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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.