Triple
T30172154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Connected Forces Initiative |
E766948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military interoperability program |
C10566
|
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 interoperability program Context triple: [NATO Connected Forces Initiative, instanceOf, military interoperability program]
-
A.
military program
chosen
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
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.
military program category
A military program category is a classification grouping related defense initiatives, projects, or activities based on their purpose, function, or capability area within an armed forces structure.
-
D.
military assistance program
A military assistance program is an organized initiative through which one nation or entity provides training, equipment, funding, or advisory support to strengthen the defense capabilities of another.
-
E.
military training mission component
A military training mission component is a discrete, structured element of a training operation—such as a task, phase, or exercise module—designed to develop, assess, or reinforce specific skills, tactics, or objectives.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:24 p.m.