Triple
T23410455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark County Coroner’s Office |
E560053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medicolegal death investigation agency |
C25635
|
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: medicolegal death investigation agency Context triple: [Clark County Coroner’s Office, instanceOf, medicolegal death investigation agency]
-
A.
death investigation authority
chosen
A death investigation authority is an official body or agency responsible for determining the cause, manner, and circumstances of deaths, particularly those that are sudden, unexpected, or legally significant.
-
B.
medical examiner's office
A medical examiner's office is a governmental facility where forensic pathologists investigate deaths, perform autopsies, and determine causes and manners of death, often in cases that are sudden, unexpected, or legally significant.
-
C.
forensic pathologist
A forensic pathologist is a medical doctor who investigates deaths by examining bodies, performing autopsies, and analyzing medical and legal evidence to determine the cause and manner of death.
-
D.
court medical service
A court medical service is a specialized unit that provides medical evaluations, expert testimony, and health-related support to the judicial system for use in legal proceedings and decisions.
-
E.
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.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:38 p.m.