Triple
T10117702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO cyber structures |
E223204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO capability area |
C16053
|
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 capability area Context triple: [NATO cyber structures, instanceOf, NATO capability area]
-
A.
NATO capability
A NATO capability is a specific military, political, or logistical asset, function, or competence that member states collectively develop, maintain, and coordinate to fulfill the Alliance’s strategic objectives and operational requirements.
-
B.
military capability area
chosen
A military capability area is a distinct domain of military functions, resources, and competencies grouped together to achieve specific defense and operational objectives.
-
C.
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.
-
D.
component of NATO command structure
A component of NATO command structure is an organizational entity—such as a headquarters, command, or specialized unit—responsible for planning, directing, and coordinating specific military or strategic functions within the Alliance’s integrated chain of command.
-
E.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:04 p.m.