Triple
T22918352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Dew |
E568790
|
entity |
| Predicate | notableMarketingTheme |
P48415
|
FINISHED |
| Object | extreme sports imagery |
—
|
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: extreme sports imagery | Statement: [Mountain Dew, notableMarketingTheme, extreme sports imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMarketingTheme Context triple: [Mountain Dew, notableMarketingTheme, extreme sports imagery]
-
A.
hasMarketingTheme
chosen
Indicates that an entity is associated with or characterized by a particular marketing theme or campaign concept.
-
B.
notableTheme
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
C.
campaignTheme
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
D.
notableMarketPositioning
Indicates that an entity holds a distinctive or strategically significant position within a particular market or competitive landscape.
-
E.
typicalMarketingEmphasis
Indicates that an entity’s marketing efforts characteristically focus on or prioritize a particular theme, feature, or message.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807b254c8190bb84596dcacaa35e |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.