Triple
T15466996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 PARA |
E372055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battalion of the Parachute Regiment |
C13431
|
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: battalion of the Parachute Regiment Context triple: [4 PARA, instanceOf, battalion of the Parachute Regiment]
-
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.
battalion of the Welsh Guards
A battalion of the Welsh Guards is a major operational unit of this British Army infantry regiment, composed of several companies of soldiers trained and organized for ceremonial duties and frontline combat operations.
-
C.
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.
-
D.
airborne infantry battalion
chosen
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.
-
E.
reconnaissance regiment
A reconnaissance regiment is a military unit specialized in gathering intelligence on enemy forces and terrain, typically using mobility, stealth, and advanced surveillance equipment to support larger formations.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:33 a.m.