Triple
T10839817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Višegrad massacres |
E255854
|
entity |
| Predicate | typeOfAtrocity |
P95406
|
FINISHED |
| Object | ethnically motivated violence |
—
|
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: ethnically motivated violence | Statement: [Višegrad massacres, typeOfAtrocity, ethnically motivated violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAtrocity Context triple: [Višegrad massacres, typeOfAtrocity, ethnically motivated violence]
-
A.
natureOfAtrocities
chosen
Indicates the specific type or character of atrocities associated with an event, action, or entity.
-
B.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
C.
timeOfMassViolence
Indicates the specific time at which an act or event of mass violence occurred.
-
D.
massacreOccurred
Indicates that a large-scale, deliberate killing of multiple individuals took place in a specific event or context.
-
E.
genocide
Indicates the deliberate and systematic destruction, in whole or in part, of a national, ethnic, racial, or religious group.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7470204548190ba0c724dd9367712 |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.