Triple
T31810637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian 1st Parachute Battalion |
E811994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parachute battalion |
C19365
|
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: parachute battalion Context triple: [Hungarian 1st Parachute Battalion, instanceOf, parachute battalion]
-
A.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of key objectives behind enemy lines.
-
B.
paratrooper unit
chosen
A paratrooper unit is a specialized military formation trained and equipped to deploy from aircraft by parachute to conduct airborne assaults, rapid insertions, and operations behind enemy lines.
-
C.
airborne infantry battalion
An airborne infantry battalion is a highly mobile, lightly equipped military unit trained and organized to deploy rapidly by air and conduct combat operations, often via parachute or air assault, to seize and hold key terrain behind or ahead of front lines.
-
D.
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.
-
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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:43 p.m.