Triple
T32482320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI case management systems |
E830143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement records system |
C19088
|
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: law enforcement records system Context triple: [FBI case management systems, instanceOf, law enforcement records system]
-
A.
law enforcement system
A law enforcement system is an organized framework of agencies, processes, and technologies designed to prevent, detect, investigate, and respond to violations of laws while upholding public safety and legal rights.
-
B.
law enforcement data
Law enforcement data is information collected, generated, or used by policing and criminal justice agencies about incidents, individuals, activities, and operations for the purposes of investigation, public safety, and legal compliance.
-
C.
criminal justice information system
chosen
A criminal justice information system is an integrated platform that collects, manages, and shares data related to crimes, offenders, victims, and justice processes among law enforcement, courts, and correctional agencies.
-
D.
law enforcement resource
A law enforcement resource is any personnel, equipment, technology, information, or funding allocated to support the prevention, investigation, and enforcement of laws and public safety.
-
E.
official record system
An official record system is a structured, authoritative repository and management framework for creating, storing, tracking, and preserving formal documents and data that serve as the definitive source of truth for an organization or jurisdiction.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:58 a.m.