Triple

T32253505
Position Surface form Disambiguated ID Type / Status
Subject Forensic Services (Detroit Police Department) E823943 entity
Predicate handlesEvidenceType P172641 FINISHED
Object fingerprints LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: fingerprints | Statement: [Forensic Services (Detroit Police Department), handlesEvidenceType, fingerprints]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: handlesEvidenceType
Context triple: [Forensic Services (Detroit Police Department), handlesEvidenceType, fingerprints]
  • A. evidenceTypeHandled chosen
    Indicates that an entity is responsible for processing or managing a particular type or category of evidence.
  • B. evidenceHandling
    Indicates how evidence is collected, processed, stored, and transferred within an investigation or legal context.
  • C. usedEvidenceType
    Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
  • D. hasEvidenceItem
    Indicates that there exists a specific piece of evidence supporting, illustrating, or justifying the associated entity or claim.
  • E. hasProcessEvidence
    Indicates that there is supporting evidence for a process or procedure associated with the subject in relation to the object.
  • F. None of above.

Provenance (3 batches)

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_69f3490db0748190bfef6e50c95d39d3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 12:41 a.m.