Triple
T6313584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepsi Max |
E141561
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Pepsi Max Vanilla |
E141745
|
NE 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: Pepsi Max Vanilla | Statement: [Pepsi Max, hasVariant, Pepsi Max Vanilla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pepsi Max Vanilla Context triple: [Pepsi Max, hasVariant, Pepsi Max Vanilla]
-
A.
Pepsi Vanilla
chosen
Pepsi Vanilla is a flavored cola soft drink that combines the classic taste of Pepsi with added vanilla flavoring.
-
B.
Pepsi Max Cherry
Pepsi Max Cherry is a cherry-flavored, sugar-free cola variant of Pepsi Max marketed as a low-calorie soft drink.
-
C.
Pepsi Max Ginger
Pepsi Max Ginger is a sugar-free, ginger-flavoured cola variant produced by PepsiCo under the Pepsi Max brand.
-
D.
Pepsi Mango
Pepsi Mango is a flavored cola soft drink that combines the taste of classic Pepsi with a sweet mango flavor.
-
E.
Pepsi Lime
Pepsi Lime is a citrus-flavored variation of the Pepsi soft drink that combines cola with a hint of lime.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a075dc8190acf7ec010cb4b00c |
completed | March 22, 2026, 9:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6385ef7c48190bc81711856977330 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:28 p.m.