Triple

T35628264
Position Surface form Disambiguated ID Type / Status
Subject KO Show E1029514 entity
Predicate hostAlignment P39832 FINISHED
Object varies between heel and face Kevin Owens 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: varies between heel and face Kevin Owens | Statement: [KO Show, hostAlignment, varies between heel and face Kevin Owens]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hostAlignment
Context triple: [KO Show, hostAlignment, varies between heel and face Kevin Owens]
  • A. hasAlignment chosen
    Indicates that one entity shares or exhibits a particular orientation, stance, or compatibility in relation to another entity or standard.
  • B. requiresAlignment
    Indicates that one entity depends on another entity being properly aligned or brought into a specified alignment condition before the relationship or action can occur.
  • C. basedOnAlignmentOf
    Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
  • D. supportsAlignment
    Indicates that one entity is compatible with and can properly function or operate in conjunction with a specified alignment, configuration, or standard.
  • E. laterAlignedWith
    Indicates that one entity becomes aligned with or matches another entity at a later point in time, rather than initially.
  • 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_69f76e07bb0c8190968ea2d836fc42c9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f17362c8190b20e45051307b16c completed May 3, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.