Triple

T38551859
Position Surface form Disambiguated ID Type / Status
Subject Jokey Smurf E925131 entity
Predicate typicalOutcomeOfPranks P206525 FINISHED
Object Box explodes in recipient's face 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: Box explodes in recipient's face | Statement: [Jokey Smurf, typicalOutcomeOfPranks, Box explodes in recipient's face]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOutcomeOfPranks
Context triple: [Jokey Smurf, typicalOutcomeOfPranks, Box explodes in recipient's face]
  • A. Prank Encounters
    Indicates a relationship where one party orchestrates a deceptive or surprising prank scenario that another party unexpectedly experiences or becomes the target of.
  • B. notablePrankTarget
    Indicates that the subject is a well-known or frequent target of pranks carried out by the object.
  • C. typicalPremise
    Indicates that one situation or statement is a common or characteristic premise that typically leads to, supports, or underlies another situation or conclusion.
  • D. commonOutcomeFor
    Indicates that multiple entities share the same resulting state, effect, or consequence.
  • E. tricked
    Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
  • 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_69f76eaeb69c8190b367df9330d6f6af completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037cae084081909004d77514c5f286 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a1e32108190897356d6a7fed879 completed May 12, 2026, 7:06 p.m.
PDg Predicate description generation batch_6a037c85e308819083dd67b96f457659 completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:32 p.m.