Triple

T9695495
Position Surface form Disambiguated ID Type / Status
Subject Helmut Zemo E234638 entity
Predicate blames P25173 FINISHED
Object Avengers for destruction of Sokovia — 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: Avengers for destruction of Sokovia | Statement: [Helmut Zemo, blames, Avengers for destruction of Sokovia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: blames
Context triple: [Helmut Zemo, blames, Avengers for destruction of Sokovia]
  • A. blamedOn chosen
    Indicates that responsibility or fault for something is assigned to a particular entity.
  • B. dislikes
    Indicates that one entity has a negative feeling or aversion toward another entity.
  • C. incumbentBlamedFor
    Indicates that responsibility or fault for a situation, problem, or outcome is attributed to the current officeholder or authority in power.
  • D. by
    Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
  • E. derogatesFrom
    Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
  • 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d366c488190bc153c68fef197c2 completed April 1, 2026, 10:33 p.m.
PD Predicate disambiguation batch_69ccd5b9e93c8190947cce56a3925364 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:17 p.m.