Triple
T27665523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reorganization of Air Force reserve components |
E697216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force history event |
C12184
|
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 history event Context triple: [Reorganization of Air Force reserve components, instanceOf, United States Air Force history event]
-
A.
United States military history event
chosen
A United States military history event is a significant occurrence involving U.S. armed forces that influences the nation’s military development, strategy, policy, or historical trajectory.
-
B.
United States Air Force operation
A United States Air Force operation is a coordinated set of air, space, and cyber activities conducted by the USAF to achieve specific military or strategic objectives in support of national defense.
-
C.
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.
-
D.
United States Air Force exercise
A United States Air Force exercise is a planned training event or series of operations designed to prepare Air Force personnel, units, and systems for real-world missions by simulating combat, support, or contingency scenarios.
-
E.
United States Air Force base
A United States Air Force base is a military installation that supports Air Force operations through facilities for aircraft, personnel, training, logistics, and command and control activities.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:37 p.m.