Triple
T28720249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BHELMA III |
E730073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | helicopter maneuver battalion |
C23741
|
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: helicopter maneuver battalion Context triple: [BHELMA III, instanceOf, helicopter maneuver battalion]
-
A.
army aviation battalion
chosen
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.
-
B.
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.
-
C.
army aviation unit
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.
-
D.
combat aviation unit
A combat aviation unit is an organized group of military aircraft, aircrew, and support personnel structured to plan, execute, and sustain offensive and defensive air operations.
-
E.
United States Marine Corps helicopter squadron
A United States Marine Corps helicopter squadron is a military aviation unit that operates rotary-wing aircraft to provide assault support, reconnaissance, close air support, and other mission-critical capabilities in support of Marine Air-Ground Task Force operations.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:53 a.m.