Triple
T15466994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 PARA |
E372055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army Reserve battalion |
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: British Army Reserve battalion Context triple: [4 PARA, instanceOf, British Army Reserve battalion]
-
A.
British Army infantry regiment
A British Army infantry regiment is a historic, regionally or culturally affiliated military unit responsible for recruiting, training, and organizing soldiers into battalions for frontline ground combat and related duties.
-
B.
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.
-
C.
British provincial regiment
A British provincial regiment is a locally raised military unit in Britain’s overseas colonies, composed mainly of colonial inhabitants who served under British command, often in support roles or auxiliary forces during imperial conflicts.
-
D.
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.
-
E.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
- 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.