Triple
T10725025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 78th Aviation Troop Command |
E252918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Army aviation command |
C23740
|
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: Army aviation command Context triple: [78th Aviation Troop Command, instanceOf, Army aviation command]
-
A.
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.
-
B.
army aviation unit
chosen
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
C.
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.
-
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.
army aviation battalion
An army aviation battalion is a military unit that operates and maintains rotary- and/or fixed-wing aircraft to provide air mobility, reconnaissance, and support to 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:14 p.m.