Triple
T25637587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona Premier |
E642747
|
entity |
| Predicate | servingSizeStandard |
P164801
|
FINISHED |
| Object | 12 oz |
—
|
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: 12 oz | Statement: [Corona Premier, servingSizeStandard, 12 oz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingSizeStandard Context triple: [Corona Premier, servingSizeStandard, 12 oz]
-
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.
servingSizeAtOktoberfest
Indicates the typical quantity or portion in which something (such as food or drink) is served specifically at Oktoberfest.
-
D.
typicalPortionPerBowl
Indicates the usual or standard quantity served in a single bowl for a given item or context.
-
E.
nutritionStandard
Indicates that something complies with, or is evaluated against, a defined set of nutritional guidelines or requirements.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 21, 2026, 5:34 p.m.