Triple

T33670295
Position Surface form Disambiguated ID Type / Status
Subject Cole Trickle E862598 entity
Predicate hasRivalInFilm P188456 FINISHED
Object Rowdy Burns NE NERFINISHED

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: Rowdy Burns | Statement: [Cole Trickle, hasRivalInFilm, Rowdy Burns]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRivalInFilm
Context triple: [Cole Trickle, hasRivalInFilm, Rowdy Burns]
  • A. filmAdversaryOf
    Indicates that one film serves as an adversary, rival, or opposing counterpart to another film, such as in competition, contrast, or narrative opposition.
  • B. performedInFilmOpposite
    Indicates that two performers acted together in significant, often directly interacting roles in the same film.
  • C. alsoPlayedIn
    Indicates that an entity (such as a person or performer) participated or appeared in another work, production, or context in addition to the one already referenced.
  • D. alliedWithInFilm
    Indicates that two characters or entities are portrayed as allies or cooperating on the same side within the context of a specific film.
  • E. hasTwinActors
    Indicates that two or more actors share a twin relationship, typically portraying twin characters or being treated as twins within a given context.
  • 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
PDg Predicate description generation batch_69fba789c1188190973a919bfe2871f3 completed May 6, 2026, 8:41 p.m.
Created at: May 1, 2026, 1:42 a.m.