Triple
T7426391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Salzburg |
E171377
|
entity |
| Predicate | usesCrestFeaturing |
P21497
|
FINISHED |
| Object | two red bulls |
—
|
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: two red bulls | Statement: [Red Bull Salzburg, usesCrestFeaturing, two red bulls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCrestFeaturing Context triple: [Red Bull Salzburg, usesCrestFeaturing, two red bulls]
-
A.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
B.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
C.
logoUsedBy
Indicates that a particular logo is employed or displayed by a specific entity as part of its identity, branding, or representation.
-
D.
logoUsedIn
Indicates that a particular logo is employed or displayed within a specified context, medium, or artifact.
-
E.
symbolOnInsignia
chosen
Indicates that a particular symbol appears on or is featured as part of an insignia.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f303eb988190ba9df7946fce1c86 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.