Triple

T19993018
Position Surface form Disambiguated ID Type / Status
Subject New York City Civilian Complaint Review Board E494108 entity
Predicate typeOfMisconductReviewed P76459 FINISHED
Object excessive force 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: excessive force | Statement: [New York City Civilian Complaint Review Board, typeOfMisconductReviewed, excessive force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfMisconductReviewed
Context triple: [New York City Civilian Complaint Review Board, typeOfMisconductReviewed, excessive force]
  • A. concernsTypeOfConduct chosen
    Indicates that something is about or relates specifically to a particular type or category of conduct or behavior.
  • B. oversightType
    Indicates the specific kind or category of oversight applied to an entity or activity, such as the manner or level of supervision, review, or regulatory control involved.
  • C. subjectOfCondemnation
    Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation by another entity.
  • D. typeOfCensure
    Indicates the specific kind or category of censure applied in a given disciplinary or critical action.
  • E. accusationsOfNonComplianceBy
    Indicates that one party has formally alleged that another party has failed to meet required rules, standards, or obligations.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fe2036c8190b9f313215ad44e87 completed April 20, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69e537fd311881908448f2aea8b4812e completed April 19, 2026, 8:15 p.m.
Created at: April 11, 2026, 3:31 p.m.