Triple
T15866888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Transport Wing Aalborg |
E384736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military air transport unit |
C8693
|
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 air transport unit Context triple: [Air Transport Wing Aalborg, instanceOf, military air transport unit]
-
A.
military air transport organization
chosen
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.
-
B.
army aviation unit
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
C.
airlift squadron
An airlift squadron is a military aviation unit responsible for transporting personnel, equipment, and supplies by air to support operational, logistical, and humanitarian missions.
-
D.
army aviation corps
The army aviation corps is a military branch responsible for providing aerial support, reconnaissance, transport, and combat capabilities to ground forces using helicopters and other aircraft.
-
E.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.