Triple
T10913443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 165th Quartermaster Company |
E257758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Quartermaster company |
C28552
|
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: Quartermaster company Context triple: [165th Quartermaster Company, instanceOf, Quartermaster company]
-
A.
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.
-
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.
infantry company
An infantry company is a military unit typically composed of several platoons of foot soldiers, organized and equipped to conduct ground combat operations under a single commanding officer.
-
D.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
-
E.
brigade support battalion
A brigade support battalion is a military unit responsible for providing comprehensive logistical, maintenance, medical, and supply support to a brigade combat team to sustain its operations.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.