Triple

T14656147
Position Surface form Disambiguated ID Type / Status
Subject Fifty-Two Pickup E344112 entity
Predicate hasBlackmailPlot P115232 FINISHED
Object true 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: true | Statement: [Fifty-Two Pickup, hasBlackmailPlot, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBlackmailPlot
Context triple: [Fifty-Two Pickup, hasBlackmailPlot, true]
  • A. hasPoliticalPlot
    Indicates that the subject work contains a storyline or narrative element centered on politics, political events, or political power struggles.
  • B. blackmailedFor
    Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
  • C. blackmails
    Indicates that one entity coerces another by threatening to reveal damaging or sensitive information unless specific demands are met.
  • D. hasIllegitimateChildPlotline
    Indicates that a narrative includes a storyline involving a character having a child born outside of a legally or socially recognized partnership.
  • E. threatensToReveal
    Indicates a situation where one entity warns or intends to disclose information about another entity, typically to exert pressure or gain leverage.
  • 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_69d822e1a2cc81908e5bb93cf61ce3cc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb51a562c819098971447db4b29f7 completed April 14, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69de6576f0208190aa94d995e797ac38 completed April 14, 2026, 4:04 p.m.
PDg Predicate description generation batch_69de716c17cc8190aeb85296abee85a7 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:27 a.m.