Triple
T37787011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Able Archer 83 crisis |
E941980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military exercise-related incident |
C52026
|
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 exercise-related incident Context triple: [Able Archer 83 crisis, instanceOf, military exercise-related incident]
-
A.
military event
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
B.
NATO military exercise
chosen
A NATO military exercise is a planned, multinational training operation conducted by NATO member and partner forces to practice joint tactics, enhance interoperability, and demonstrate collective defense capabilities.
-
C.
naval exercise
A naval exercise is a planned training operation in which naval forces simulate combat, coordination, and operational scenarios to improve readiness, tactics, and interoperability.
-
D.
United States Air Force exercise
A United States Air Force exercise is a planned training event or series of operations designed to prepare Air Force personnel, units, and systems for real-world missions by simulating combat, support, or contingency scenarios.
-
E.
military involvement
Military involvement refers to the participation of a nation's armed forces in activities ranging from combat operations and peacekeeping missions to training, advisory roles, and support functions within domestic or international contexts.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.