Triple
T11477297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division Sustainment Brigade |
E272055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistics brigade |
C30085
|
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 brigade Context triple: [Division Sustainment Brigade, instanceOf, logistics brigade]
-
A.
logistics command
Logistics command is the organizational function responsible for planning, coordinating, and controlling the movement, supply, and maintenance of resources to ensure operational readiness and sustained support.
-
B.
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.
-
C.
Quartermaster company
A quartermaster company is a military logistics unit responsible for supplying, transporting, and managing essential materials, equipment, and services to support combat and support forces.
-
D.
Engineer brigade
An engineer brigade is a military unit composed of specialized engineering battalions that provide construction, mobility, counter-mobility, and survivability support to larger combat formations.
-
E.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:36 p.m.