Triple
T9386903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Special Forces |
E225926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations command structure |
C11385
|
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 operations command structure Context triple: [UK Special Forces, instanceOf, special operations command structure]
-
A.
military special operations command
chosen
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
B.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
C.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their 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.
specialized operations division
A specialized operations division is a focused organizational unit responsible for planning and executing complex, high-priority, or technically advanced missions that fall outside the scope of standard operational teams.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:45 p.m.