Triple
T8219466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europol Information System |
E192020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement 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: law enforcement database Context triple: [Europol Information System, instanceOf, law enforcement database]
-
A.
law enforcement agency network
A law enforcement agency network is an interconnected system of local, regional, and national policing and investigative bodies that share information, resources, and coordination mechanisms to prevent, detect, and respond to crime and public safety threats.
-
B.
legal database
A legal database is an organized digital repository that stores, indexes, and enables search and retrieval of legal materials such as statutes, case law, regulations, and secondary sources.
-
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 body
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
-
E.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service 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.