Triple

T25086918
Position Surface form Disambiguated ID Type / Status
Subject WCW World Tag Team Championship E628348 entity
Predicate defendedOnShow P158772 FINISHED
Object WCW Thunder NE NERFINISHED

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: WCW Thunder | Statement: [WCW World Tag Team Championship, defendedOnShow, WCW Thunder]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defendedOnShow
Context triple: [WCW World Tag Team Championship, defendedOnShow, WCW Thunder]
  • A. defendedOn
    Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
  • B. defendedAs
    Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
  • C. defendedAtEvent
    Indicates that an entity (typically a work, thesis, or position) was formally defended or argued for during a specific event.
  • D. titleDefendedBy
    Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
  • E. canBeDefendedIn
    Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
  • 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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f48b9b687881908fd87a2f5fa0b1e7 completed May 1, 2026, 11:16 a.m.
PD Predicate disambiguation batch_69f48060597c8190a4414e4e4fcb1fec completed May 1, 2026, 10:28 a.m.
PDg Predicate description generation batch_69f48b9058d081908ec9af261ee092e2 completed May 1, 2026, 11:16 a.m.
Created at: April 18, 2026, 6:23 a.m.