Triple
T36195017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome Air Logistics Center |
E1047097
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force logistics center |
C66187
|
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 logistics center Context triple: [Rome Air Logistics Center, instanceOf, United States Air Force logistics center]
-
A.
Air Force Sustainment Center (AFSC)
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.
-
B.
Air and Space Operations Center
An Air and Space Operations Center is a command and control facility that plans, directs, coordinates, and monitors air and space operations to achieve assigned military objectives.
-
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.
logistics readiness squadron
A logistics readiness squadron is a military unit responsible for planning, managing, and executing the movement, supply, and sustainment of personnel, equipment, and materiel to ensure operational readiness.
-
E.
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.
- F. None of above. chosen
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.