Triple
T35125922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Speicher massacre |
E1014301
|
entity |
| Predicate | victimSelectionCriteria |
P699
|
FINISHED |
| Object | religious affiliation |
—
|
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: religious affiliation | Statement: [Camp Speicher massacre, victimSelectionCriteria, religious affiliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimSelectionCriteria Context triple: [Camp Speicher massacre, victimSelectionCriteria, religious affiliation]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimOrder
Indicates the sequence or ranking of victims involved in an event or incident.
-
C.
victimCountPolicy
Indicates the rule or criterion used to determine how victims are counted or classified in a given context.
-
D.
victimGroup
chosen
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
E.
victimGroupContext
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.