Triple
T10442900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosse Ardeatine massacre |
E246211
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II 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: World War II war crime Context triple: [Fosse Ardeatine massacre, instanceOf, World War II 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 trial
A war crimes trial is a formal legal proceeding in which individuals or groups are prosecuted and judged for violations of the laws and customs of war, such as atrocities against civilians, prisoners of war, or other protected persons.
-
C.
war crime site
A war crime site is a specific location where serious violations of the laws and customs of war have been committed, investigated, or memorialized, often serving as evidence in legal proceedings and as a place of historical record.
-
D.
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.
-
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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:15 p.m.