Triple

T32063721
Position Surface form Disambiguated ID Type / Status
Subject Game Show in My Head E818816 entity
Predicate contestantRole P120250 FINISHED
Object follow instructions from host via earpiece 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: follow instructions from host via earpiece | Statement: [Game Show in My Head, contestantRole, follow instructions from host via earpiece]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contestantRole
Context triple: [Game Show in My Head, contestantRole, follow instructions from host via earpiece]
  • A. talentShowRole
    Indicates the specific function or position an entity holds within the context of a talent show (e.g., performer, judge, host).
  • B. roleOfCharacter
    Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
  • C. cultRole
    Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
  • D. entertainmentRole chosen
    Indicates that an entity holds a specific function or position within an entertainment context (such as a role in a performance, production, or media work).
  • E. speakerRole
    Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
  • 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_69f348fecc088190af1470afe5a969f0 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7626667f48190ad90867eb67ec582 completed May 3, 2026, 2:57 p.m.
PD Predicate disambiguation batch_69f76175d6608190b60b268e20f49ed9 completed May 3, 2026, 2:53 p.m.
Created at: May 1, 2026, 12:22 a.m.