Triple

T19489838
Position Surface form Disambiguated ID Type / Status
Subject Shankill Road bombing E487617 entity
Predicate perpetratorMotive P65261 FINISHED
Object attempt to assassinate UDA leadership 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: attempt to assassinate UDA leadership | Statement: [Shankill Road bombing, perpetratorMotive, attempt to assassinate UDA leadership]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: perpetratorMotive
Context triple: [Shankill Road bombing, perpetratorMotive, attempt to assassinate UDA leadership]
  • A. hasMotiveOfCriminals chosen
    Indicates that the specified motive is attributed to or associated with the criminals in question.
  • B. reasonForMurder
    Indicates the motive or underlying cause that led someone to commit a murder.
  • C. perpetratorType
    Indicates the classification or category of the entity that carried out or is responsible for a harmful, illegal, or otherwise wrongful act.
  • D. causeStatedByPerpetrators
    Indicates that the stated cause or reason for an event or action is the one explicitly given by the perpetrators themselves.
  • E. perpetratorDescription
    Indicates that the subject provides a textual description or characterization of the perpetrator involved in an act or incident.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6348ad4088190b530f47efca90165 completed April 20, 2026, 2:13 p.m.
PD Predicate disambiguation batch_69e4fd7883308190b73912a71a35a835 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:39 p.m.