Triple
T34984487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockin’ & Roastin’ Coffee |
E1008904
|
entity |
| Predicate | genreOfBranding |
P74696
|
FINISHED |
| Object | music-inspired branding |
—
|
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: music-inspired branding | Statement: [Rockin’ & Roastin’ Coffee, genreOfBranding, music-inspired branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfBranding Context triple: [Rockin’ & Roastin’ Coffee, genreOfBranding, music-inspired branding]
-
A.
brandingCategory
Indicates the classification of an entity into a specific branding-related category or type.
-
B.
brandingStyle
chosen
Indicates the specific visual and stylistic approach used to represent a brand’s identity.
-
C.
brandingFeature
Indicates that one entity serves as a branding-related characteristic, element, or attribute that helps define or distinguish another entity’s brand identity.
-
D.
brandingThrough
Indicates that one entity promotes, communicates, or shapes the identity of another entity by means of a specific brand or branding activity.
-
E.
brandingGoal
Indicates the strategic objective or desired outcome that an entity aims to achieve through its branding efforts.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.