Triple
T36678074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firearms Unit (Kent Police) |
E905598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed response unit |
C13533
|
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: armed response unit Context triple: [Firearms Unit (Kent Police), instanceOf, armed response unit]
-
A.
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.
-
B.
special weapons and tactics unit
chosen
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.
-
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.
assault gun brigade
An assault gun brigade is a military formation equipped primarily with assault guns or self-propelled artillery, organized to provide direct fire support to infantry and armored units against enemy fortifications, armor, and strongpoints.
-
E.
armed raid
An armed raid is a sudden, coordinated attack carried out by individuals or groups using weapons to seize control, steal assets, or intimidate targets, often with minimal warning and rapid execution.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.