Triple

T11152514
Position Surface form Disambiguated ID Type / Status
Subject General Leonid Pushkin E263820 entity
Predicate antagonistStatus P98122 FINISHED
Object initially suspected antagonist 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: initially suspected antagonist | Statement: [General Leonid Pushkin, antagonistStatus, initially suspected antagonist]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: antagonistStatus
Context triple: [General Leonid Pushkin, antagonistStatus, initially suspected antagonist]
  • A. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • B. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • C. antagonistInvolved
    Indicates that an antagonist participates in, influences, or is otherwise actively involved in the referenced event or situation.
  • D. isCentralAntagonist
    Indicates that an entity serves as the primary opposing force or main villain driving conflict against the protagonist or central characters.
  • E. primaryAntagonistType
    Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
  • F. None of above. chosen

Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e872ffbc8190b8a3bbd912115342 completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75ce71944819089eee9b5c9283cbd completed April 9, 2026, 8:01 a.m.
PDg Predicate description generation batch_69d7706116248190a87440bec3960884 completed April 9, 2026, 9:24 a.m.
Created at: April 8, 2026, 9:28 p.m.