Triple
T4675035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Fugitive Task Forces |
E103657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fugitive apprehension 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: fugitive apprehension unit Context triple: [Joint Fugitive Task Forces, instanceOf, fugitive apprehension 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 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.
-
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.
criminal investigation unit
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
E.
field operating agency
A field operating agency is an organizational unit that performs specialized, mission-support or operational functions for a higher headquarters, typically operating outside the main administrative structure and often dispersed geographically.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.