Triple
T19794918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettle Brand Sea Salt & Vinegar potato chips |
E475514
|
entity |
| Predicate | commonServingSize |
P137354
|
FINISHED |
| Object | 1 oz (about 28 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 oz (about 28 g) | Statement: [Kettle Brand Sea Salt & Vinegar potato chips, commonServingSize, 1 oz (about 28 g)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonServingSize Context triple: [Kettle Brand Sea Salt & Vinegar potato chips, commonServingSize, 1 oz (about 28 g)]
-
A.
servingSizeAtOktoberfest
Indicates the typical quantity or portion in which something (such as food or drink) is served specifically at Oktoberfest.
-
B.
typicalPortionPerBowl
Indicates the usual or standard quantity served in a single bowl for a given item or context.
-
C.
carbohydratesPer12Ounces
Indicates the amount of carbohydrates contained in a 12-ounce serving of a given item.
-
D.
typicalIngredientRatio
Indicates the usual proportional relationship between different ingredients used together in a preparation or mixture.
-
E.
hasCalories
Indicates that an entity contains a specified amount of caloric energy.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c659088190928fa4c9264135d3 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.