Triple
T22351585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallschirmjäger-Regiment 2 |
E552542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paratrooper regiment |
C16998
|
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: paratrooper regiment Context triple: [Fallschirmjäger-Regiment 2, instanceOf, paratrooper regiment]
-
A.
paratrooper unit
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.
-
B.
parachute infantry regiment
chosen
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.
-
C.
paratroop commander
A paratroop commander is a military leader responsible for planning, coordinating, and directing airborne infantry operations from deployment through mission completion.
-
D.
airborne engineer regiment
An airborne engineer regiment is a specialized military unit trained and equipped to deploy by air and conduct engineering tasks such as obstacle breaching, fortification, mobility, and infrastructure support in austere or contested environments.
-
E.
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.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.