Triple

T26390233
Position Surface form Disambiguated ID Type / Status
Subject Red Bull multi-club system E663390 entity
Predicate usesSharedBrandElements P48444 FINISHED
Object Red Bull name 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: Red Bull name | Statement: [Red Bull multi-club system, usesSharedBrandElements, Red Bull name]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSharedBrandElements
Context triple: [Red Bull multi-club system, usesSharedBrandElements, Red Bull name]
  • A. hasBrandIdentityElement
    Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
  • B. sharesBrandingWith chosen
    Indicates that two entities use the same or closely related branding elements, such as name, logo, or visual identity.
  • C. usesBrandColor
    Indicates that one entity applies or displays another entity’s official brand color in its appearance, design, or materials.
  • D. usesSameBrandFamilyAs
    Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
  • E. hasCoBrand
    Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
  • 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f674e06c9481909ed0ea736408f0d7 completed May 2, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69f673c2f81c8190bf369226306eef09 completed May 2, 2026, 9:59 p.m.
Created at: April 26, 2026, 11:25 p.m.