Triple
T2301863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23 SAS |
E51750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Special Air Service regiment |
C2497
|
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: Special Air Service regiment Context triple: [23 SAS, instanceOf, Special Air Service regiment]
-
A.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
-
B.
airborne infantry division
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
-
C.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
D.
special operations aviation command
A special operations aviation command is a military organization that provides specialized, often clandestine air support—such as infiltration, exfiltration, resupply, and close air support—for special operations forces in high-risk or sensitive missions.
-
E.
Royal Air Force squadron
A Royal Air Force squadron is a military aviation unit comprising aircraft, aircrew, and support personnel organized under a specific command structure to perform designated operational, training, or support roles.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:49 p.m.