Triple
T2277099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21 SAS |
E51195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regiment of the British Army Reserve |
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: regiment of the British Army Reserve Context triple: [21 SAS, instanceOf, regiment of the British Army Reserve]
-
A.
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.
-
B.
organisational unit of the UK Ministry of Defence
An organisational unit of the UK Ministry of Defence is a formally defined structural entity within the department, such as a command, agency, directorate, or division, responsible for specific defence-related functions, resources, and decision-making.
-
C.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
D.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.