Triple
T27729374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster Energy |
E697388
|
entity |
| Predicate | hasServingSizeVariant |
P192207
|
FINISHED |
| Object | 16 fl oz can |
—
|
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: 16 fl oz can | Statement: [Monster Energy, hasServingSizeVariant, 16 fl oz can]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServingSizeVariant Context triple: [Monster Energy, hasServingSizeVariant, 16 fl oz can]
-
A.
commonServingSize
Indicates that two or more food items share the same standard or typical serving size used for comparison or labeling.
-
B.
marketedAsServing
Indicates that something is promoted or advertised as providing service to a particular audience, purpose, or function.
-
C.
servingSizeStandard
Indicates that there is a standard or officially defined serving size associated with an item.
-
D.
hasVariantIngredient
Indicates that one ingredient is an alternative or substitute form of another ingredient used in a product or formulation.
-
E.
hasServiceVariations
Indicates that a service is offered in multiple distinct versions, options, or configurations that differ in some defined characteristics.
- F. None of above. chosen
Provenance (4 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:10 p.m.