Triple

T38537785
Position Surface form Disambiguated ID Type / Status
Subject Blood Tribe Police Service E924745 entity
Predicate usesPolicingApproach P21773 FINISHED
Object trauma-informed policing 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: trauma-informed policing | Statement: [Blood Tribe Police Service, usesPolicingApproach, trauma-informed policing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesPolicingApproach
Context triple: [Blood Tribe Police Service, usesPolicingApproach, trauma-informed policing]
  • A. policyApproach
    Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
  • B. policingModel chosen
    Indicates the approach, strategy, or framework used to organize and conduct policing activities or law enforcement operations.
  • C. hasDisciplinaryApproach
    Indicates that an entity employs, follows, or is characterized by a particular disciplinary method, framework, or approach.
  • D. usedToApproach
    Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
  • E. usedPolicy
    Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
  • 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_69f76eadeac081909cdfdd0474cb6765 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
Created at: May 3, 2026, 4:32 p.m.