Triple
T9775964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canberra Pact |
E237247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence cooperation agreement |
C824
|
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: defence cooperation agreement Context triple: [Canberra Pact, instanceOf, defence cooperation 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.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
C.
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.
-
D.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
E.
collective defense activity
A collective defense activity is a coordinated action undertaken by multiple individuals or groups to protect shared interests, resources, or members from perceived threats or harm.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:26 p.m.