Triple
T17302444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caffeine Free Dr Pepper |
E420071
|
entity |
| Predicate | sugarContentVariant |
P52605
|
FINISHED |
| Object | regular sugar version |
—
|
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: regular sugar version | Statement: [Caffeine Free Dr Pepper, sugarContentVariant, regular sugar version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sugarContentVariant Context triple: [Caffeine Free Dr Pepper, sugarContentVariant, regular sugar version]
-
A.
sweetenerVariant
Indicates that one sweetening agent is a specific type, version, or alternative form of another sweetening agent.
-
B.
hasSugarFreeVariant
chosen
Indicates that an item has a corresponding version or option that is formulated without sugar.
-
C.
sugarContentCategory
Indicates the classification of something based on how much sugar it contains (e.g., low, medium, or high sugar content).
-
D.
hasSugarContent
Indicates that one entity possesses or contains a specified amount or level of sugar.
-
E.
sweetenerType
Indicates the specific kind or category of sweetener associated with or used in relation to an entity.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fba938819084333764b868bd83 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.