Triple
T33724352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Rasella attack |
E864101
|
entity |
| Predicate | retaliationVictims |
P699
|
FINISHED |
| Object | Italian civilians |
—
|
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: Italian civilians | Statement: [Via Rasella attack, retaliationVictims, Italian civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retaliationVictims Context triple: [Via Rasella attack, retaliationVictims, Italian civilians]
-
A.
honorsVictimOf
Indicates that one entity pays tribute or respect to another entity who has suffered harm, loss, or injustice.
-
B.
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.
-
C.
victimGroup
chosen
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
D.
victimsOfCrime
Indicates that the subject has suffered harm or loss as a result of a criminal act committed by the object.
-
E.
belligerentSideOfVictims
Indicates that the referenced party is the side or faction to which the victims in a conflict or hostile situation belong.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:44 a.m.