Triple
T20801117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Declaration 2012 |
E512041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense cooperation agreement |
C42371
|
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 cooperation agreement Context triple: [Washington Declaration 2012, instanceOf, defense cooperation agreement]
-
A.
bilateral military agreement
chosen
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
B.
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.
-
C.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
-
D.
defense industry joint venture
A defense industry joint venture is a collaborative business entity formed by two or more organizations to jointly develop, produce, or support military and security-related products or services, sharing resources, risks, and profits.
-
E.
defense cost-sharing agreement
A defense cost-sharing agreement is a contractual arrangement in which two or more parties agree to allocate and reimburse expenses related to legal defense in connection with specified claims or proceedings.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:39 p.m.