Triple
T2086685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Special Forces Command (Airborne) |
E45367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations headquarters |
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 operations headquarters Context triple: [1st Special Forces Command (Airborne), instanceOf, special operations headquarters]
-
A.
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.
-
B.
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.
-
C.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
D.
rescue unit
A rescue unit is an organized team equipped and trained to respond rapidly to emergencies, providing aid, protection, and extraction of people or animals from dangerous or life-threatening situations.
-
E.
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.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:41 p.m.