Triple
T2570132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapland Air Command |
E57644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional air command |
C10545
|
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: regional air command Context triple: [Lapland Air Command, instanceOf, regional air command]
-
A.
Tactical air force
A tactical air force is a military aviation organization focused on providing direct air support, interdiction, and battlefield air operations in coordination with ground and naval forces within a specific theater of operations.
-
B.
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.
-
C.
special operations aviation command
A special operations aviation command is a military organization that provides specialized, often clandestine air support—such as infiltration, exfiltration, resupply, and close air support—for special operations forces in high-risk or sensitive missions.
-
D.
military air transport organization
A military air transport organization is a structured entity responsible for planning, coordinating, and executing the airlift of personnel, equipment, and supplies to support military operations and strategic objectives.
-
E.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.