Triple
T5162016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Air Force |
E116456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic bombing force |
C6540
|
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: strategic bombing force Context triple: [Independent Air Force, instanceOf, strategic bombing force]
-
A.
Strategic bombing force
chosen
A strategic bombing force is a military aviation unit organized, equipped, and trained to conduct long-range, high-impact bombing campaigns against an adversary’s critical infrastructure, industry, and strategic assets to weaken their capacity and will to wage war.
-
B.
strategic bombing campaign
A strategic bombing campaign is a sustained aerial offensive aimed at weakening an enemy’s war-making capacity and morale by targeting key industrial, military, and infrastructural assets rather than solely engaging frontline forces.
-
C.
bomber group
A bomber group is a military aviation unit composed of multiple bomber squadrons organized to conduct coordinated bombing missions against strategic or tactical targets.
-
D.
strategic bomber
A strategic bomber is a long-range military aircraft designed to deliver large payloads of bombs or missiles against distant, high-value strategic targets such as infrastructure, industry, and command centers.
-
E.
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.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:44 p.m.