Triple
T8219467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europol Information System |
E192020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal intelligence 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 intelligence system Context triple: [Europol Information System, instanceOf, criminal intelligence 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.
criminal investigation unit
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
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.
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.
signals intelligence system
A signals intelligence system is an integrated set of tools, sensors, and processes designed to intercept, collect, analyze, and exploit electronic signals and communications for intelligence and security purposes.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.