Triple

T33476952
Position Surface form Disambiguated ID Type / Status
Subject Buck Commander: Protected by Under Armour E857347 entity
Predicate hasTitleSponsorship P24881 FINISHED
Object Under Armour 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: Under Armour | Statement: [Buck Commander: Protected by Under Armour, hasTitleSponsorship, Under Armour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTitleSponsorship
Context triple: [Buck Commander: Protected by Under Armour, hasTitleSponsorship, Under Armour]
  • A. hasTitleSponsor chosen
    Indicates that one entity serves as the primary (title) sponsor for another entity, typically giving its name to the sponsored event, organization, or property.
  • B. hasTitleSponsorHistorically
    Indicates that an entity has served as the primary (title) sponsor of another entity during some period in the past.
  • C. includesSponsorship
    Indicates that one entity’s involvement, agreement, or arrangement explicitly involves sponsorship provided by another entity.
  • D. hasSponsor
    Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
  • E. hasFictionalSponsor
    Indicates that an entity is sponsored or endorsed by a sponsor that is fictional rather than real.
  • 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_69f3497472508190b300ebd3fd402367 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd592e48cc81909d754cc6c4bd99ae completed May 8, 2026, 3:31 a.m.
PD Predicate disambiguation batch_69fd58b7f9b881909dc099b28d567784 completed May 8, 2026, 3:30 a.m.
Created at: May 1, 2026, 1:38 a.m.