Triple
T34898434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infantry Brigade Combat Team |
E1006506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | modular brigade |
C56563
|
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: modular brigade Context triple: [Infantry Brigade Combat Team, instanceOf, modular brigade]
-
A.
Maneuver Enhancement Brigade
A Maneuver Enhancement Brigade is a modular U.S. Army support formation designed to enhance the freedom of movement, protection, and sustainment of combat forces by integrating engineer, military police, CBRN, and other enabling capabilities.
-
B.
armored brigade combat team
An armored brigade combat team is a highly mobile, heavily armored combined-arms military formation designed to conduct offensive and defensive ground operations using tanks, mechanized infantry, artillery, and support units.
-
C.
assault gun brigade
An assault gun brigade is a military formation equipped primarily with assault guns or self-propelled artillery, organized to provide direct fire support to infantry and armored units against enemy fortifications, armor, and strongpoints.
-
D.
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.
-
E.
brigade-level formation
chosen
A brigade-level formation is a mid-sized military unit, typically composed of several battalions and supporting elements, capable of independent operations under a unified command.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.