Triple
T1187278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Defence and Economic Co-operation Treaty of 1950 |
E25275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence pact |
C89
|
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 pact Context triple: [Joint Defence and Economic Co-operation Treaty of 1950, instanceOf, defence pact]
-
A.
collective defense agreement
chosen
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.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
defence estate
A defence estate is the collective portfolio of land, buildings, infrastructure, and facilities owned, leased, or managed by a nation's defence organization to support military operations, training, administration, and logistics.
-
D.
truce
A truce is a mutually agreed temporary cessation of hostilities between opposing parties, typically to allow negotiation, humanitarian relief, or a pause in conflict.
-
E.
border defense system
A border defense system is an integrated network of physical barriers, surveillance technologies, personnel, and response protocols designed to monitor, control, and protect a nation's boundaries from unauthorized crossings and external threats.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.