Triple
T30125433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOLMES investigation system |
E765681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | police investigation management 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: police investigation management system Context triple: [HOLMES investigation system, instanceOf, police investigation management system]
-
A.
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.
-
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.
police operations center
A police operations center is a centralized facility where law enforcement personnel monitor incidents, coordinate field units, manage communications, and make real-time decisions to ensure public safety and effective response.
-
D.
polis
A polis is an ancient Greek city-state, functioning as an independent political, social, and religious community centered on an urban core and its surrounding territory.
-
E.
law enforcement system
A law enforcement system is an organized framework of agencies, processes, and technologies designed to prevent, detect, investigate, and respond to violations of laws while upholding public safety and legal rights.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:14 p.m.