Triple
T1750029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Strategic Airlift Capability |
E38418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational military program |
C4089
|
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: multinational military program Context triple: [NATO Strategic Airlift Capability, instanceOf, multinational military program]
-
A.
military rearmament program
A military rearmament program is a coordinated, government-directed initiative to expand, modernize, or restore a nation’s armed forces and weaponry in response to strategic, political, or security objectives.
-
B.
military procurement programme
A military procurement programme is an organized, often long-term government initiative to identify, acquire, and manage the development, purchase, and deployment of equipment, systems, and services for the armed forces.
-
C.
multinational mission mechanism
chosen
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
D.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
-
E.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.