Triple
T17364579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Tactical Leadership Programme |
E422154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO organization |
C11966
|
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: NATO organization Context triple: [NATO Tactical Leadership Programme, instanceOf, NATO organization]
-
A.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
B.
NATO member state
A NATO member state is a sovereign country that has formally joined the North Atlantic Treaty Organization, committing to mutual defense, political consultation, and military cooperation with other member nations under the alliance’s founding treaty.
-
C.
NATO administrative division
chosen
A NATO administrative division is an organizational unit within the North Atlantic Treaty Organization responsible for managing specific functions, regions, or operational domains to support the alliance’s political, military, and logistical activities.
-
D.
Warsaw Pact body
A Warsaw Pact body is an organizational entity, such as a committee, command structure, or coordinating institution, established under the Warsaw Pact to manage its military, political, or administrative functions among member states.
-
E.
NATO outreach mechanism
A NATO outreach mechanism is a structured process or tool through which NATO engages, communicates, and cooperates with non-member states, organizations, and publics to advance its security objectives and partnerships.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.