Triple
T17152818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanilla Coke |
E416263
|
entity |
| Predicate | competitor |
P1375
|
FINISHED |
| Object | Pepsi 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 Vanilla | Statement: [Vanilla Coke, competitor, Pepsi Vanilla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pepsi Vanilla Context triple: [Vanilla Coke, competitor, Pepsi 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 Raspberry
Pepsi Max Raspberry is a sugar-free, raspberry-flavoured cola variant of the Pepsi Max soft drink line.
-
C.
Pepsi Max Cherry
Pepsi Max Cherry is a cherry-flavored, sugar-free cola variant of Pepsi Max marketed as a low-calorie soft drink.
-
D.
Pepsi Lime
Pepsi Lime is a citrus-flavored variation of the Pepsi soft drink that combines cola with a hint of lime.
-
E.
Pepsi Mango
Pepsi Mango is a flavored cola soft drink that combines the taste of classic Pepsi with a sweet mango flavor.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40861e08190bad1a3ec87691132 |
completed | April 18, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01415d19288190beb3c94da2ce8c0e |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.