Triple
T342814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutual Defense Agreement (1958) |
E6872
|
entity |
| Predicate | typeOfCooperation |
P1854
|
FINISHED |
| Object | exchange of classified nuclear information |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: exchange of classified nuclear information | Statement: [Mutual Defense Agreement (1958), typeOfCooperation, exchange of classified nuclear information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCooperation Context triple: [Mutual Defense Agreement (1958), typeOfCooperation, exchange of classified nuclear information]
-
A.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
B.
collaborationModel
chosen
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
C.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
D.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
E.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
- F. None of above.
Provenance (3 batches)
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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eafef8c88190a5932eb2c6ac4a5d |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.