Triple

T29040641
Position Surface form Disambiguated ID Type / Status
Subject Hey Vern, It's Ernest! E737986 entity
Predicate intendedBroadcastSchedule P138340 FINISHED
Object weekly series 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: weekly series | Statement: [Hey Vern, It's Ernest!, intendedBroadcastSchedule, weekly series]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedBroadcastSchedule
Context triple: [Hey Vern, It's Ernest!, intendedBroadcastSchedule, weekly series]
  • A. primaryBroadcastSchedule chosen
    Indicates the main or default schedule according to which a broadcast is planned or transmitted.
  • B. intendedBroadcastBlock
    Indicates that a particular content item is planned or scheduled to be aired within a specific broadcast time block.
  • C. broadcastScheduleChange
    Indicates that a modification has been made to the planned timing or lineup of a broadcast.
  • D. intendedForBroadcast
    Indicates that something is meant or designated to be transmitted to an audience via a broadcast medium.
  • E. broadcastTimeSlot
    Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
  • 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_69f077efb3848190b41574e1670f6ae2 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: April 28, 2026, 10:01 a.m.