Triple
T27659463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Enforcement Division (Arizona Game and Fish Department) |
E697081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wildlife law enforcement 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: wildlife law enforcement unit Context triple: [Law Enforcement Division (Arizona Game and Fish Department), instanceOf, wildlife law enforcement unit]
-
A.
wildlife law enforcement program
A wildlife law enforcement program is an organized governmental or institutional initiative that detects, prevents, and prosecutes violations of wildlife protection laws to conserve species and habitats.
-
B.
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.
-
C.
wildlife crime laboratory
A wildlife crime laboratory is a specialized forensic facility that analyzes biological, genetic, and physical evidence to investigate and support the prosecution of illegal activities involving wild animals and plants.
-
D.
fish and wildlife agency
A fish and wildlife agency is a governmental or tribal organization responsible for conserving, managing, and regulating fish, wildlife, and their habitats for ecological health and public benefit.
-
E.
wildlife protection law
A wildlife protection law is a legal framework that regulates human activities to conserve wild animal and plant species, their habitats, and biodiversity, often through prohibitions, permits, and enforcement mechanisms.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:35 p.m.