Triple
T4503474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian special forces |
E101276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special forces |
C10260
|
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 forces Context triple: [Russian special forces, instanceOf, special forces]
-
A.
naval special forces
chosen
Naval special forces are elite military units trained and equipped to conduct specialized maritime, amphibious, and coastal operations, often involving reconnaissance, direct action, and counterterrorism in and from the sea.
-
B.
military special operations command
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.
-
C.
specialist corps
A specialist corps is a dedicated group of highly trained experts within a larger organization or system, formed to perform complex, technical, or niche tasks that require advanced, domain-specific skills.
-
D.
special weapons and tactics unit
A special weapons and tactics unit is a highly trained law enforcement team equipped and organized to handle high-risk operations such as hostage rescues, armed standoffs, and counterterrorism incidents beyond the capabilities of regular police patrols.
-
E.
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.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:01 p.m.