Triple
T2553285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolution Fresh |
E56674
|
entity |
| Predicate | ownedBrandOf |
P6092
|
FINISHED |
| Object | Starbucks beverage portfolio |
—
|
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: Starbucks beverage portfolio | Statement: [Evolution Fresh, ownedBrandOf, Starbucks beverage portfolio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedBrandOf Context triple: [Evolution Fresh, ownedBrandOf, Starbucks beverage portfolio]
-
A.
parentBrand
chosen
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
B.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
distributedBrand
Indicates that one entity serves as a distributor or reseller for the brand of another entity.
-
D.
relatedBrand
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
-
E.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.