Triple

T35597547
Position Surface form Disambiguated ID Type / Status
Subject Destiny: The Taken King E1028674 entity
Predicate addsCampaign P183437 FINISHED
Object The Taken King story campaign 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: The Taken King story campaign | Statement: [Destiny: The Taken King, addsCampaign, The Taken King story campaign]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: addsCampaign
Context triple: [Destiny: The Taken King, addsCampaign, The Taken King story campaign]
  • A. plannedCampaign
    Indicates that an entity has designed and scheduled a campaign to be executed in the future.
  • B. campaignConnection
    Indicates a relationship where two entities are linked through participation in, association with, or influence within the same campaign or related campaigns.
  • C. launchCampaign
    Indicates initiating and putting into operation a planned promotional or marketing campaign.
  • D. campaignManager
    Indicates that one entity serves as the manager or coordinator responsible for planning, executing, and overseeing a campaign on behalf of another entity.
  • E. supportedCampaignOf
    Indicates that one entity actively backed, promoted, or provided assistance to the campaign associated with 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_69f76e0598dc8190a6a093e904b9aa70 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f7340e4819092a1a47f7028e63f completed May 3, 2026, 7:18 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
PDg Predicate description generation batch_69f79ec14ce08190b22cee0b40d33743 completed May 3, 2026, 7:15 p.m.
Created at: May 3, 2026, 4:05 p.m.