Triple
T3358123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 509th Composite Group |
E70653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army Air Forces unit |
C9555
|
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 Army Air Forces unit Context triple: [509th Composite Group, instanceOf, United States Army Air Forces unit]
-
A.
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.
-
B.
United States Army Air Forces major command
A United States Army Air Forces major command was a top-level organizational entity responsible for directing, coordinating, and supporting large-scale air operations, training, logistics, and administrative functions within the USAAF during its existence.
-
C.
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.
-
D.
Luftwaffe bomber wing
A Luftwaffe bomber wing is a large, operational German air force unit composed of multiple bomber groups, responsible for planning and executing coordinated bombing missions.
-
E.
air force wing
chosen
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.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.