Triple

T12867791
Position Surface form Disambiguated ID Type / Status
Subject Swedish Armed Forces Cyber Defence E307766 entity
Predicate instanceOf P0 FINISHED
Object branch of the Swedish Armed Forces C27333 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: branch of the Swedish Armed Forces
Context triple: [Swedish Armed Forces Cyber Defence, instanceOf, branch of the Swedish Armed Forces]
  • A. component of the Swedish Armed Forces chosen
    A component of the Swedish Armed Forces is an organizational subdivision, such as a branch, unit, or support element, that contributes specific capabilities and resources to Sweden’s national defense and military operations.
  • B. Swedish Army regiment
    A Swedish Army regiment is a military unit of the Swedish Army responsible for organizing, training, and maintaining combat-ready forces within a specific branch, function, or geographic area.
  • C. branch of the Bundeswehr
    A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
  • D. branch of the Soviet Armed Forces
    A branch of the Soviet Armed Forces is a major organizational component responsible for a specific domain of military operations—such as ground, naval, air, or strategic missile forces—within the overall Soviet military structure.
  • E. branch of the French Armed Forces
    A branch of the French Armed Forces is a major organizational component, such as the Army, Navy, Air and Space Force, or Gendarmerie, responsible for specific military roles, capabilities, and operations under national defense policy.
  • 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.