Triple

T178682
Position Surface form Disambiguated ID Type / Status
Subject Uniformed Services Bureau E3633 entity
Predicate lawEnforcementType P3734 FINISHED
Object special jurisdiction police 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: special jurisdiction police | Statement: [Uniformed Services Bureau, lawEnforcementType, special jurisdiction police]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lawEnforcementType
Context triple: [Uniformed Services Bureau, lawEnforcementType, special jurisdiction police]
  • A. securityAgency
    Indicates that one entity functions as a security agency responsible for protection, surveillance, or enforcement activities in relation to another entity.
  • B. policePrecinct
    Indicates that a specified location, building, or area functions as or is designated as a police precinct.
  • C. typeOfJurisdiction chosen
    Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
  • D. typeOfDefense
    Indicates the specific kind or category of defense employed or possessed in a given context.
  • E. governmentBranch
    Indicates that one entity functions as an official division or branch within the structure of a government.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a25900709c8190a65e778936be5dd5 completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a2566b53d481909c0ed40dd3719e8c completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.