Triple
T33724350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Rasella attack |
E864101
|
entity |
| Predicate | retaliationType |
P113442
|
FINISHED |
| Object | mass execution |
—
|
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: mass execution | Statement: [Via Rasella attack, retaliationType, mass execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retaliationType Context triple: [Via Rasella attack, retaliationType, mass execution]
-
A.
retaliationForm
chosen
Indicates the manner or type in which retaliation is carried out in response to a prior action or offense.
-
B.
patentRetaliation
Indicates that one party takes or threatens adverse action against another in response to the other’s exercise or enforcement of patent rights.
-
C.
typeOfCensure
Indicates the specific kind or category of censure applied in a given disciplinary or critical action.
-
D.
compensatoryType
Indicates the specific category or nature of compensation associated with an action, obligation, or remedy in the relationship.
-
E.
negativeType
Indicates that one entity is classified as a negative, undesirable, or disfavored type in relation to another or within a given context.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.