Triple
T2559619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO–Russia relations |
E57210
|
entity |
| Predicate | NATOCooperationSuspended |
P40464
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [NATO–Russia relations, NATOCooperationSuspended, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOCooperationSuspended Context triple: [NATO–Russia relations, NATOCooperationSuspended, 2014]
-
A.
moveOfNATOFrom
Indicates a movement or deployment action carried out by NATO originating from a specified location.
-
B.
diplomaticRelationsSeveredYear
Indicates the year in which formal diplomatic relations between the referenced parties were officially severed.
-
C.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
D.
NATOAccessionYear
Indicates the year in which an entity formally became a member of NATO.
-
E.
hasParticipatingNATOAllies
Indicates that an entity is involved in an activity, operation, or arrangement together with one or more NATO member states as allies.
- F. None of above. chosen
Provenance (4 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd35b216881908f4ef32d1c1e5080 |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.