Triple
T35152485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speicher massacre |
E1015030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ISIS war crime |
C178
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ISIS war crime Context triple: [Speicher massacre, instanceOf, ISIS war crime]
-
A.
warCrime
chosen
A warCrime is an unlawful act committed during armed conflict that violates international humanitarian law, such as targeting civilians, mistreating prisoners, or using prohibited weapons.
-
B.
war crimes investigation
A war crimes investigation is a systematic inquiry into alleged violations of the laws and customs of war, aimed at collecting evidence, identifying responsible individuals or entities, and supporting potential legal prosecution or accountability mechanisms.
-
C.
war crime defendant
A war crime defendant is an individual formally accused of violating the laws and customs of war, such as committing atrocities against civilians, prisoners of war, or other protected persons, and is subject to investigation and trial in a competent court or tribunal.
-
D.
war criminal
A war criminal is an individual who has committed serious violations of the laws and customs of war, such as targeting civilians, mistreating prisoners, or using prohibited weapons, and can be held personally responsible under international law.
-
E.
war crime directive
A war crime directive is an explicit order or policy issued by an authority that instructs or authorizes the commission of actions that violate international humanitarian law during armed conflict.
- F. None of above.
Provenance (1 batch)
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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.