Triple

T32644630
Position Surface form Disambiguated ID Type / Status
Subject The Tribal Chief E834566 entity
Predicate gimmickType P155186 FINISHED
Object dominant champion 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: dominant champion | Statement: [The Tribal Chief, gimmickType, dominant champion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: gimmickType
Context triple: [The Tribal Chief, gimmickType, dominant champion]
  • A. gimmick
    Indicates that an entity uses or features a novel, attention-grabbing trick or device primarily intended to attract interest rather than provide substantive value.
  • B. associatedWithGimmick chosen
    Indicates that one entity is connected or linked to a particular gimmick, typically as a defining feature, strategy, or promotional element.
  • C. promotionGimmick
    Indicates a relationship where something is used as a special tactic or device to attract attention or boost interest in a promotion.
  • D. maskOrGimmick
    Indicates that one entity serves as a mask, disguise, or gimmick used by another entity, typically to conceal identity or create a particular impression.
  • E. hasTrickType
    Indicates that an entity (such as a trick or maneuver) is associated with a specific type or category of trick.
  • 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_69f3492e773c81908afc10651e46cad3 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c775d6188190b236fc4f89a11b61 completed May 3, 2026, 3:56 a.m.
PD Predicate disambiguation batch_69f6c3f617c08190a70ba880210f908c completed May 3, 2026, 3:41 a.m.
Created at: May 1, 2026, 1:07 a.m.