Triple
T14917828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftwaffe formations |
E371426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air force organizational 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: air force organizational structure Context triple: [Luftwaffe formations, instanceOf, air force organizational 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 Air Force organization
A United States Air Force organization is a structured unit or entity within the Air Force, such as a squadron, group, wing, or command, established to perform specific operational, support, or administrative missions in support of national defense objectives.
-
C.
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.
-
D.
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.
-
E.
air force formation
An air force formation is an organized arrangement of multiple military aircraft flying together in a coordinated pattern to achieve tactical, strategic, or ceremonial objectives.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:32 a.m.