Triple
T7196275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 101st Combat Aviation Brigade |
E168623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat aviation brigade |
C11717
|
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 aviation brigade Context triple: [101st Combat Aviation Brigade, instanceOf, combat aviation brigade]
-
A.
U.S. Army aviation brigade
chosen
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.
-
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.
army aviation corps
The army aviation corps is a military branch responsible for providing aerial support, reconnaissance, transport, and combat capabilities to ground forces using helicopters and other aircraft.
-
D.
U.S. Army aviation battalion
A U.S. Army aviation battalion is a military unit that organizes, operates, and sustains multiple helicopter or fixed-wing aircraft companies to provide air assault, reconnaissance, transport, medical evacuation, and support capabilities to ground forces.
-
E.
airborne corps
An airborne corps is a large military formation composed primarily of paratrooper and air-transportable units, organized and equipped to conduct large-scale airborne operations behind or across enemy lines.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
Created at: March 27, 2026, 2:51 p.m.