Triple
T4026982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviazione Legionaria |
E83614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | expeditionary air corps |
C15176
|
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: expeditionary air corps Context triple: [Aviazione Legionaria, instanceOf, expeditionary air corps]
-
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.
airborne corps
An airborne corps is a large military formation composed primarily of paratrooper and air-transportable units, organized and equipped to conduct large-scale airborne operations behind or across enemy lines.
-
C.
auxiliary air force
An auxiliary air force is a supplementary aviation component that supports a nation's primary air force through roles such as training, logistics, civil defense, and non-combat operations, often staffed by reservists or volunteers.
-
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.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.