Triple
T6182318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Security Deployments |
E137971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized security unit |
C3496
|
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: specialized security unit Context triple: [Mobile Security Deployments, instanceOf, specialized security unit]
-
A.
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.
-
B.
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.
-
C.
law enforcement unit
chosen
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
D.
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.
-
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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:19 p.m.