Triple
T19332610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Air Force (RM12 variant) |
E483533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air force branch engine user |
C41942
|
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: air force branch engine user Context triple: [Swedish Air Force (RM12 variant), instanceOf, air force branch engine user]
-
A.
air engineering squadron
An air engineering squadron is a military unit responsible for the maintenance, repair, testing, and technical support of aircraft and related aerospace systems to ensure their operational readiness and safety.
-
B.
military aircraft engine
A military aircraft engine is a high-performance propulsion system designed to power combat and support aircraft, optimized for thrust, reliability, maneuverability, and operation under extreme conditions.
-
C.
aviation support unit
An aviation support unit is an organizational entity that provides maintenance, logistics, ground handling, and operational assistance to ensure the effective and safe functioning of aircraft and flight operations.
-
D.
airborne engineer regiment
An airborne engineer regiment is a specialized military unit trained and equipped to deploy by air and conduct engineering tasks such as obstacle breaching, fortification, mobility, and infrastructure support in austere or contested environments.
-
E.
air force wing
An air force wing is a major operational unit composed of multiple squadrons and support elements, organized to conduct and sustain specific air missions under a unified command.
- F. None of above. chosen
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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.