Triple
T6107640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diet Pepsi |
E136154
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Diet Pepsi Lime |
E136154
|
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: Diet Pepsi Lime | Statement: [Diet Pepsi, hasVariant, Diet Pepsi Lime]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Diet Pepsi Lime Context triple: [Diet Pepsi, hasVariant, Diet Pepsi Lime]
-
A.
Diet Pepsi
chosen
Diet Pepsi is a low-calorie, sugar-free cola soft drink produced by PepsiCo as an alternative to its regular Pepsi beverage.
-
B.
Pepsi Lime
Pepsi Lime is a citrus-flavored variation of the Pepsi soft drink that combines cola with a hint of lime.
-
C.
Diet Coke
Diet Coke is a popular sugar-free, low-calorie soft drink that serves as the primary diet cola offering from The Coca-Cola Company.
-
D.
Pepsi Vanilla
Pepsi Vanilla is a flavored cola soft drink that combines the classic taste of Pepsi with added vanilla flavoring.
-
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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b81fad081909b622cafc6d51249 |
completed | March 22, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c13598c54c8190b3701de83005875c |
completed | March 23, 2026, 12:44 p.m. |
Created at: March 22, 2026, 4:13 p.m.