Triple

T38570070
Position Surface form Disambiguated ID Type / Status
Subject Cleaver E929239 entity
Predicate inUniverseMarketing P194930 FINISHED
Object straight-to-video style horror-gangster hybrid 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: straight-to-video style horror-gangster hybrid | Statement: [Cleaver, inUniverseMarketing, straight-to-video style horror-gangster hybrid]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseMarketing
Context triple: [Cleaver, inUniverseMarketing, straight-to-video style horror-gangster hybrid]
  • A. inUniverse
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • B. inUniverseDemand
    Indicates that one entity requires or seeks something from another within the context of a specific fictional or defined universe.
  • C. inUniverseInterest
    Indicates that one entity has an interest in or affinity for another entity within the context of a specific fictional or defined universe.
  • D. inUniverseMall
    Indicates that one entity is located within or belongs to the setting of a fictional or in-universe mall.
  • E. inUniverseMaker
    Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
  • 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_69f76ebd2248819083978362d81fa35e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 completed May 8, 2026, 7:18 a.m.
PD Predicate disambiguation batch_69fd8d8a16f08190b9e880901bfa44fe completed May 8, 2026, 7:15 a.m.
PDg Predicate description generation batch_69fd8e5e9ca48190890a2caddc1f9f5c completed May 8, 2026, 7:18 a.m.
Created at: May 3, 2026, 4:32 p.m.