Triple
T24825883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftwaffe (planned) |
E621188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | projected air force structure |
C18803
|
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: projected air force structure Context triple: [Luftwaffe (planned), instanceOf, projected air force structure]
-
A.
Air Force organization
chosen
An Air Force organization is a structured unit within an air force responsible for planning, directing, and executing air and space operations, support, or administration to achieve military objectives.
-
B.
United States Space Force organizational system
The United States Space Force organizational system is the structured arrangement of commands, field units, roles, and processes designed to plan, conduct, and support space operations in alignment with national defense objectives.
-
C.
air army
An air army is a large, organized military aviation formation comprising multiple air corps, divisions, and support units responsible for conducting and coordinating air operations within a designated theater.
-
D.
former air force
A former air force is a previously active national military aviation branch that has been disbanded, merged, or otherwise ceased to operate as an independent air service.
-
E.
United States Air Force project
A United States Air Force project is an organized, time-bound initiative undertaken by the USAF to research, develop, test, or implement capabilities, systems, or operations in support of its strategic and tactical missions.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:05 a.m.