Triple
T18144151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 332nd Fighter Group |
E434340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army Air Forces fighter group |
C14294
|
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 fighter group Context triple: [332nd Fighter Group, instanceOf, United States Army Air Forces fighter group]
-
A.
United States Army Air Corps unit
A United States Army Air Corps unit is a military aviation organization, active primarily between 1926 and 1947, responsible for operating aircraft, conducting air missions, and supporting U.S. Army operations before the establishment of the independent U.S. Air Force.
-
B.
Luftwaffe fighter unit
A Luftwaffe fighter unit is a World War II-era German air force formation composed of fighter aircraft and their crews, organized to achieve air superiority, escort missions, and defensive operations.
-
C.
fighter group
chosen
A fighter group is a military aviation unit composed of multiple fighter squadrons, organized to conduct coordinated air combat and support operations under a unified command.
-
D.
United States Army Air Service squadron
A United States Army Air Service squadron is a military aviation unit of the U.S. Army during and shortly after World War I, responsible for organizing, training, and deploying aircraft and aircrews for combat, reconnaissance, and support missions.
-
E.
fighter squadron
A fighter squadron is a military aviation unit composed of multiple fighter aircraft and their personnel, organized to conduct air-to-air and air-to-ground combat 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.