Triple
T30690204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 36 MDG |
E781303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Air Force medical group |
C13062
|
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: U.S. Air Force medical group Context triple: [36 MDG, instanceOf, U.S. Air Force medical group]
-
A.
United States Air Force medical unit
chosen
A United States Air Force medical unit is an organized group within the USAF responsible for providing medical care, aeromedical evacuation, and health support to Air Force personnel and operations in both peacetime and combat environments.
-
B.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
-
C.
United States Air Force maintenance group
A United States Air Force maintenance group is an organizational unit responsible for managing, coordinating, and executing aircraft and equipment maintenance to ensure mission-ready capabilities for its assigned wing.
-
D.
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.
-
E.
Air Force squadron
An Air Force squadron is a military aviation unit composed of multiple aircraft and personnel, organized to perform specific operational, training, or support 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.