Triple
T16363622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City Air Logistics Complex |
E397377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Air logistics complex |
C14561
|
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: Air logistics complex Context triple: [Oklahoma City Air Logistics Complex, instanceOf, Air logistics complex]
-
A.
military air transport organization
A military air transport organization is a structured entity responsible for planning, coordinating, and executing the airlift of personnel, equipment, and supplies to support military operations and strategic objectives.
-
B.
Air Force Sustainment Center (AFSC)
chosen
The Air Force Sustainment Center (AFSC) is a major U.S. Air Force organization responsible for providing depot maintenance, supply chain management, and sustainment support to ensure the readiness and availability of air and space weapon systems.
-
C.
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.
-
D.
naval air station
A naval air station is a military airfield operated by a navy, providing facilities for the operation, maintenance, training, and support of naval aircraft and their personnel.
-
E.
deployable air command and control centre
A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.