Triple

T31953955
Position Surface form Disambiguated ID Type / Status
Subject Battle of Sokovia E815853 entity
Predicate defenseStrategyOfAvengers P59761 FINISHED
Object containment of Ultron drones 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: containment of Ultron drones | Statement: [Battle of Sokovia, defenseStrategyOfAvengers, containment of Ultron drones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defenseStrategyOfAvengers
Context triple: [Battle of Sokovia, defenseStrategyOfAvengers, containment of Ultron drones]
  • A. avenges
    Indicates that one entity retaliates or exacts retribution against another entity on behalf of a wrong or harm done to a third party.
  • B. roleInAvengers
    Indicates that an entity has a specific role or membership status within the Avengers team.
  • C. roleInAgeOfUltron
    Indicates that an entity has a specific role or participation in the context of "Age of Ultron" (e.g., the film or storyline).
  • D. hasDefenseStrategy chosen
    Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
  • E. defensivePlan
    Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
  • 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_69f348f4ec708190abbb2a7c3ed58844 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: May 1, 2026, 12:08 a.m.