Triple
T10805248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 648th Maneuver Enhancement Brigade |
E254945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maneuver enhancement brigade |
C20917
|
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: maneuver enhancement brigade Context triple: [648th Maneuver Enhancement Brigade, instanceOf, maneuver enhancement brigade]
-
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.
airborne infantry brigade
An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
-
C.
Engineer brigade
chosen
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.
-
D.
missile defense brigade
A missile defense brigade is a military unit responsible for detecting, tracking, and intercepting incoming missile threats to protect designated forces, assets, and territories.
-
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.
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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.