Triple
T16963457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Events Management Unit |
E411485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal law enforcement support 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: federal law enforcement support unit Context triple: [Special Events Management Unit, instanceOf, federal law enforcement support unit]
-
A.
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.
-
B.
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.
-
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.
airborne law enforcement unit
An airborne law enforcement unit is a specialized police or security team that uses aircraft to conduct surveillance, support ground operations, pursue suspects, and perform search and rescue or public safety missions from the air.
-
E.
maritime law enforcement unit
A maritime law enforcement unit is an organized body responsible for enforcing laws, ensuring security, and protecting resources within a nation’s territorial waters and maritime zones.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.