Triple
T4350172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Measures Agreements on cost sharing |
E98004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense cost-sharing agreement |
C15768
|
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: defense cost-sharing agreement Context triple: [Special Measures Agreements on cost sharing, instanceOf, defense cost-sharing agreement]
-
A.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
B.
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.
-
C.
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.
-
D.
multistate settlement agreement
A multistate settlement agreement is a coordinated legal resolution in which multiple state authorities jointly negotiate and finalize terms with one or more parties to resolve common claims or regulatory issues across their jurisdictions.
-
E.
peace clause
A peace clause is a contractual or legal provision in which parties agree to refrain from certain actions or disputes for a specified period, typically to maintain stability or allow negotiations.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:15 p.m.