Triple
T12867790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Armed Forces Cyber Defence |
E307766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber defence unit |
C2497
|
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 cyber defence unit Context triple: [Swedish Armed Forces Cyber Defence, instanceOf, military cyber defence unit]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
C.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
-
D.
military capability development organization
A military capability development organization is an entity responsible for identifying future operational needs and systematically designing, testing, and integrating new doctrines, technologies, and force structures to enhance a military’s effectiveness.
-
E.
organisational unit of the UK Ministry of Defence
An organisational unit of the UK Ministry of Defence is a formally defined structural entity within the department, such as a command, agency, directorate, or division, responsible for specific defence-related functions, resources, and decision-making.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:38 p.m.