Triple
T3909291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Sustainment Center |
E87282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major Command Subordinate Unit |
C14560
|
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: Major Command Subordinate Unit Context triple: [Air Force Sustainment Center, instanceOf, Major Command Subordinate Unit]
-
A.
subordinate unified combatant command
A subordinate unified combatant command is a command established by a unified combatant command to conduct operations on a continuing basis within a specific functional or geographic area under the authority of that parent unified command.
-
B.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
U.S. Army aviation brigade
A U.S. Army aviation brigade is a large, modular combat unit that provides coordinated helicopter and unmanned aircraft support for assault, reconnaissance, transport, and logistical missions in support of ground forces.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.