Triple
T338239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanford Federal Facility Agreement and Consent Order |
E6775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legally binding consent order |
C3152
|
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: legally binding consent order Context triple: [Hanford Federal Facility Agreement and Consent Order, instanceOf, legally binding consent order]
-
A.
legal pledge
A legal pledge is a formal commitment, often documented and enforceable by law, in which a party promises to fulfill specific obligations or refrain from certain actions, typically as security or assurance in a legal or contractual context.
-
B.
social contract
A social contract is an implicit or explicit agreement among individuals in a society to surrender some freedoms and accept certain rules or authority in exchange for protection, order, and mutual benefit.
-
C.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
D.
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.
-
E.
standardized license
A standardized license is a pre-defined, widely accepted legal agreement that sets uniform terms and conditions for using, sharing, or distributing a product, service, or intellectual property.
- 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.