Triple
T17195155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dirección estratégica del Ejército del Aire y del Espacio |
E417330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | función de dirección estratégica militar |
C4796
|
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: función de dirección estratégica militar Context triple: [dirección estratégica del Ejército del Aire y del Espacio, instanceOf, función de dirección estratégica militar]
-
A.
military strategy
chosen
Military strategy is the high-level planning and directing of armed forces and resources to achieve political and military objectives in war or conflict.
-
B.
strategic military route
A strategic military route is a planned path or corridor used to move troops, equipment, and supplies efficiently while maximizing operational advantage and minimizing vulnerability to enemy action.
-
C.
military government function
A military government function is an activity or responsibility carried out by armed forces to administer, control, or support governance and public order, especially in times of conflict, occupation, or emergency.
-
D.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
E.
military-technical authority
A military-technical authority is an entity or individual empowered to make decisions and provide expert guidance on the development, deployment, and regulation of military technologies and related operational capabilities.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.