Triple

T35808423
Position Surface form Disambiguated ID Type / Status
Subject The Boss 'n' Hug Connection E1035162 entity
Predicate competedForBrand P154357 FINISHED
Object Raw tag team division 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: Raw tag team division | Statement: [The Boss 'n' Hug Connection, competedForBrand, Raw tag team division]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competedForBrand
Context triple: [The Boss 'n' Hug Connection, competedForBrand, Raw tag team division]
  • A. competedInBrand chosen
    Indicates that an entity took part in a competition, event, or contest that was organized, sponsored, or associated with a particular brand.
  • B. brandCompetedOn
    Indicates that two brands have competed against each other in the same market, category, or competitive context.
  • C. usesCompetitionBrand
    Indicates that one entity makes use of a product, service, or brand that belongs to a competing company or organization.
  • D. competedFor
    Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
  • E. competitiveBrandName
    Indicates that one brand name is in a competitive relationship with another brand name in the same market or product space.
  • 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_69f76e1762408190b885a8456862e372 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: May 3, 2026, 4:06 p.m.