Triple
T16363579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFSC |
E397376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistics and sustainment organization |
C13448
|
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: logistics and sustainment organization Context triple: [AFSC, instanceOf, logistics and sustainment organization]
-
A.
logistics brigade
A logistics brigade is a military unit responsible for planning, coordinating, and executing the supply, transportation, maintenance, and support services needed to sustain combat and support forces.
-
B.
U.S. Army sustainment command
The U.S. Army Sustainment Command is the organization responsible for providing logistics, supply, maintenance, and distribution support to ensure Army forces are equipped and sustained during training, deployment, and combat operations worldwide.
-
C.
military support organization
chosen
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
D.
acquisition support organization
An acquisition support organization is a specialized entity that provides expertise, resources, and services to plan, manage, and execute procurement and acquisition activities efficiently and in compliance with relevant policies and regulations.
-
E.
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.
- 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.