Triple
T32610945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forensic Identification Unit (York Regional Police) |
E833649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | forensic identification unit |
C2354
|
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: forensic identification unit Context triple: [Forensic Identification Unit (York Regional Police), instanceOf, forensic identification unit]
-
A.
crime laboratory
A crime laboratory is a specialized facility where scientific techniques and analyses are applied to physical evidence to support criminal investigations and legal proceedings.
-
B.
regional forensic science platform
A regional forensic science platform is an integrated system that connects laboratories, law enforcement, and judicial entities within a geographic area to manage, analyze, and share forensic data and case information securely and efficiently.
-
C.
forensic scientist
A forensic scientist is a professional who applies scientific methods and techniques to analyze physical evidence from crime scenes to help reconstruct events and support legal investigations.
-
D.
criminal investigation unit
chosen
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.
-
E.
forensic science network
A forensic science network is an interconnected system of professionals, laboratories, databases, and technologies that collaboratively collect, analyze, share, and interpret scientific evidence to support criminal investigations and legal proceedings.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.