Triple
T7203738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nespresso |
E148612
|
entity |
| Predicate | advertisingFocus |
P18486
|
FINISHED |
| Object | premium lifestyle advertising campaigns |
—
|
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: premium lifestyle advertising campaigns | Statement: [Nespresso, advertisingFocus, premium lifestyle advertising campaigns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisingFocus Context triple: [Nespresso, advertisingFocus, premium lifestyle advertising campaigns]
-
A.
brandFocus
chosen
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
B.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
C.
advertisingLocation
Indicates the place or medium where an advertisement is displayed or presented.
-
D.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
E.
mediaFocus
Indicates that the primary attention, coverage, or emphasis of a media source is directed toward a particular entity or topic.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e94bfb2c81909ab492757435fce4 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.