Triple

T37224024
Position Surface form Disambiguated ID Type / Status
Subject Montana Max E922958 entity
Predicate oftenAntagonizes P129276 FINISHED
Object Buster Bunny and friends 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: Buster Bunny and friends | Statement: [Montana Max, oftenAntagonizes, Buster Bunny and friends]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenAntagonizes
Context triple: [Montana Max, oftenAntagonizes, Buster Bunny and friends]
  • A. antagonisticArc chosen
    Indicates a relationship in which one entity consistently opposes, harms, or works against another over the course of a conflict or storyline.
  • B. antagonistStatus
    Indicates that an entity holds an opposing or adversarial role, often acting as the main source of conflict relative to another entity or objective.
  • C. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • D. antagonistInvolved
    Indicates that an antagonist participates in, influences, or is otherwise actively involved in the referenced event or situation.
  • E. antagonisticInteractionWith
    Indicates a hostile or oppositional interaction in which one entity acts against, harms, or obstructs another.
  • 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_69f76ea7f0008190b31b8e30f3d05a71 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe1fd637c08190aa95cd2478c278cb completed May 8, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69fe19344bb481909b5e2144155e4add completed May 8, 2026, 5:11 p.m.
Created at: May 3, 2026, 4:15 p.m.