Triple
T4800981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 Pact of Madrid with the United States |
E106830
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military 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: military cooperation agreement Context triple: [1953 Pact of Madrid with the United States, instanceOf, military 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.
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.
-
D.
multinational military forum
A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
-
E.
trilateral security partners
Trilateral security partners are three sovereign entities that formally coordinate defense, intelligence, and strategic policies to enhance their collective security and regional or global stability.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.