Triple
T6182320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Security Deployments |
E137971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protective operations team |
C8231
|
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: protective operations team Context triple: [Mobile Security Deployments, instanceOf, protective operations team]
-
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.
counterterrorism task force
A counterterrorism task force is a specialized, multi-agency group organized to prevent, detect, and respond to terrorist threats and activities through intelligence gathering, operational coordination, and targeted interventions.
-
C.
operational unit
chosen
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
-
D.
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.
-
E.
parliamentary security organization
A parliamentary security organization is a specialized body responsible for protecting the legislature’s members, staff, visitors, facilities, and information while supporting the safe and orderly conduct of parliamentary business.
- 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.