Triple
T33841108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensure Max Protein |
E867359
|
entity |
| Predicate | sugarPerServing |
P26918
|
FINISHED |
| Object | 1 g |
—
|
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: 1 g | Statement: [Ensure Max Protein, sugarPerServing, 1 g]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sugarPerServing Context triple: [Ensure Max Protein, sugarPerServing, 1 g]
-
A.
carbohydratesPer12Ounces
Indicates the amount of carbohydrates contained in a 12-ounce serving of a given item.
-
B.
sweetenerType
Indicates the specific kind or category of sweetener associated with or used in relation to an entity.
-
C.
commonServingSize
Indicates that two or more food items share the same standard or typical serving size used for comparison or labeling.
-
D.
hasSugarContent
chosen
Indicates that one entity possesses or contains a specified amount or level of sugar.
-
E.
servingSizeStandard
Indicates that there is a standard or officially defined serving size associated with an item.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7004f4d9c8190b6517493f08084d4 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.