Triple

T31826654
Position Surface form Disambiguated ID Type / Status
Subject Forensics Unit (Tampa Police Department) E812413 entity
Predicate evidenceTypeHandled 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: [Forensics Unit (Tampa Police Department), evidenceTypeHandled, fingerprints]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: evidenceTypeHandled
Context triple: [Forensics Unit (Tampa Police Department), evidenceTypeHandled, fingerprints]
  • A. usedEvidenceType
    Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
  • B. hasEvidenceItem
    Indicates that there exists a specific piece of evidence supporting, illustrating, or justifying the associated entity or claim.
  • C. providesEvidenceFor
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • D. hasProcessEvidence
    Indicates that there is supporting evidence for a process or procedure associated with the subject in relation to the object.
  • E. informationTypeHandled
    Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
  • F. None of above. chosen

Provenance (4 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_69f348e97fa48190aa06286962af6dee completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b034bc74819091250f91ba5174c0 completed May 3, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69f6aca59d4881908d14ed47962703bd completed May 3, 2026, 2:02 a.m.
PDg Predicate description generation batch_69f6af7d92008190aead47eaae8cc091 completed May 3, 2026, 2:14 a.m.
Created at: April 30, 2026, 11:46 p.m.