Triple
T18878856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSNI Tactical Support Group |
E461762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical support 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: tactical support unit Context triple: [PSNI Tactical Support Group, instanceOf, tactical support unit]
-
A.
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.
-
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.
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.
-
D.
combat support battalion
A combat support battalion is a military unit that provides specialized capabilities—such as engineering, intelligence, communications, and logistics—to enhance and sustain the combat effectiveness of frontline forces.
-
E.
brigade support battalion
A brigade support battalion is a military unit responsible for providing comprehensive logistical, maintenance, medical, and supply support to a brigade combat team to sustain its operations.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.