Triple
T21557464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Transportation Corps |
E531930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat service support branch |
C14836
|
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: combat service support branch Context triple: [U.S. Army Transportation Corps, instanceOf, combat service support branch]
-
A.
combat support battalion
A combat support battalion is a military unit that provides specialized capabilities—such as engineering, intelligence, communications, and logistics—to enhance and sustain the combat effectiveness of frontline forces.
-
B.
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.
-
C.
military support organization
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.
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.
-
E.
branch of service
chosen
A branch of service is a distinct organizational subdivision within a nation’s armed forces or public service, defined by its specific mission, capabilities, and operational domain.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:29 p.m.