Triple
T8128122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Joint Incident Response Unit |
E189786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CBRN response unit |
C4743
|
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: CBRN response unit Context triple: [Canadian Joint Incident Response Unit, instanceOf, CBRN response unit]
-
A.
rescue unit
chosen
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.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
-
C.
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.
-
D.
armored recovery vehicle
An armored recovery vehicle is a heavily protected, tracked or wheeled military support vehicle designed to recover, tow, repair, and maintain disabled or damaged armored fighting vehicles on or near the battlefield.
-
E.
Humvee variant
A Humvee variant is a specific configuration of the High Mobility Multipurpose Wheeled Vehicle (HMMWV) tailored with distinct equipment, armor, or mission-specific modifications to fulfill particular operational roles.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:34 p.m.