Triple
T22761335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Commando Royal Engineers |
E562997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Engineers regiment |
C1740
|
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: Royal Engineers regiment Context triple: [24 Commando Royal Engineers, instanceOf, Royal Engineers regiment]
-
A.
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.
-
B.
army engineer
An army engineer is a military specialist who designs, constructs, and maintains infrastructure and systems to support combat operations and logistical needs in diverse and often hostile environments.
-
C.
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.
-
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.
British Army organizational element
chosen
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:26 p.m.