Triple
T30962500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Police National Computer |
E788866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal records database |
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: criminal records database Context triple: [Police National Computer, instanceOf, criminal records database]
-
A.
criminal history monitoring service
A criminal history monitoring service continuously tracks and updates individuals’ criminal records across relevant jurisdictions, alerting authorized parties to new charges, convictions, or changes in status.
-
B.
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.
-
C.
collection of crime reports
A collection of crime reports represents an organized set of documented incidents detailing alleged criminal activities, including relevant facts, participants, locations, times, and investigative outcomes.
-
D.
crime data collection program
A crime data collection program is a software system that systematically gathers, validates, and stores crime-related information from various sources to support analysis, reporting, and decision-making.
-
E.
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.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.