Triple
T1916878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirteenth Air Force |
E40037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force formation |
C6097
|
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: United States Air Force formation Context triple: [Thirteenth Air Force, instanceOf, United States Air Force formation]
-
A.
United States Air Force organization
chosen
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.
-
B.
United States Air Force wing
A United States Air Force wing is a major operational unit, typically composed of multiple groups and squadrons, organized to perform a specific mission such as combat, mobility, or support under a single commander.
-
C.
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.
-
D.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
-
E.
United States Air Force position
A United States Air Force position is a defined role within the Air Force organizational structure that specifies an individual’s duties, responsibilities, rank requirements, and place in the chain of command to support the service’s mission.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.