Triple
T16363624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City Air Logistics Complex |
E397377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maintenance, repair, and overhaul facility |
C4156
|
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: Maintenance, repair, and overhaul facility Context triple: [Oklahoma City Air Logistics Complex, instanceOf, Maintenance, repair, and overhaul facility]
-
A.
maintenance facility
chosen
A maintenance facility is a dedicated location equipped with tools, resources, and personnel for inspecting, repairing, and servicing equipment, vehicles, or infrastructure to ensure their proper functioning and longevity.
-
B.
maintenance, repair and overhaul provider
A maintenance, repair and overhaul provider is an organization that performs inspection, servicing, repair, and refurbishment of equipment or systems to ensure their continued safe, reliable, and efficient operation.
-
C.
private automotive facility
A private automotive facility is a secure, non-public site equipped for storing, maintaining, testing, or customizing vehicles, typically owned or controlled by an individual, organization, or manufacturer.
-
D.
munitions facility
A munitions facility is an industrial site where explosive weapons, ammunition, and related components are manufactured, assembled, stored, and sometimes tested under controlled conditions.
-
E.
ordnance facility
An ordnance facility is a specialized site where military weapons, ammunition, and related explosive materials are manufactured, stored, maintained, and sometimes tested under controlled conditions.
- 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.