Triple

T16291881
Position Surface form Disambiguated ID Type / Status
Subject Jesse Hubbard E395542 entity
Predicate hasDramaticStorylines P21484 FINISHED
Object faked death 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: faked death | Statement: [Jesse Hubbard, hasDramaticStorylines, faked death]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDramaticStorylines
Context triple: [Jesse Hubbard, hasDramaticStorylines, faked death]
  • A. hasDramaticElements chosen
    Indicates that something contains features or qualities characteristic of drama, such as heightened emotion, tension, or conflict.
  • B. hasDramaticStructure
    Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
  • C. hasDramaticProduction
    Indicates that an entity is associated with or features a specific dramatic production (such as a play, performance, or staged work).
  • D. hasDramaticPurpose
    Indicates that something serves a specific dramatic function or role within a narrative or performance.
  • E. hasDramaticStyle
    Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
  • 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_69d87f22c7248190a54c949738441e2e completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24919345881909ba4e7fe2e59340f completed April 17, 2026, 2:52 p.m.
PD Predicate disambiguation batch_69e219f68d308190b71c1601303f0628 completed April 17, 2026, 11:31 a.m.
Created at: April 10, 2026, 5:05 a.m.