Triple

T16315571
Position Surface form Disambiguated ID Type / Status
Subject Tree of Life – Or L'Simcha Congregation E396163 entity
Predicate victimGroupIn2018Attack P699 FINISHED
Object Jewish worshippers 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: Jewish worshippers | Statement: [Tree of Life – Or L'Simcha Congregation, victimGroupIn2018Attack, Jewish worshippers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: victimGroupIn2018Attack
Context triple: [Tree of Life – Or L'Simcha Congregation, victimGroupIn2018Attack, Jewish worshippers]
  • A. victimGroup chosen
    Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
  • B. victimGroupContext
    Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
  • C. victimGroupHelped
    Indicates that assistance, support, or aid was provided to a group identified as victims.
  • D. coVictim
    Indicates that two or more entities are victims in the same harmful event or incident.
  • E. allegedVictimOf
    Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
  • 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_69d87f255b788190a400eba031dd85d8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e288de57cc81908cec93309347c385 completed April 17, 2026, 7:24 p.m.
PD Predicate disambiguation batch_69e219fc72c881909d452274e7af8238 completed April 17, 2026, 11:31 a.m.
Created at: April 10, 2026, 5:06 a.m.