Triple
T29968730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interpol Information System |
E761260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal intelligence 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 intelligence database Context triple: [Interpol Information System, instanceOf, criminal intelligence database]
-
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 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.
-
C.
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.
-
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.
counterterrorism database
A counterterrorism database is a centralized, secure repository that stores, organizes, and enables analysis of information related to terrorist organizations, individuals, activities, and incidents to support prevention, investigation, and response efforts.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:31 p.m.