Triple
T28388425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIS |
E719085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal information 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: criminal information system Context triple: [EIS, instanceOf, criminal information system]
-
A.
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.
-
B.
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.
-
C.
crime data program
A crime data program is a software system that collects, stores, analyzes, and visualizes crime-related information to support law enforcement, policy-making, and public safety decision-making.
-
D.
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.
-
E.
criminal justice institution
A criminal justice institution is an organized system or agency, such as courts, police, or correctional facilities, responsible for enforcing laws, adjudicating offenses, and administering sanctions to maintain social order and public safety.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:11 a.m.