Triple
T19842682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettle Brand Backyard Barbeque potato chips |
E476775
|
entity |
| Predicate | seasoningType |
P137544
|
FINISHED |
| Object | barbecue seasoning |
—
|
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: barbecue seasoning | Statement: [Kettle Brand Backyard Barbeque potato chips, seasoningType, barbecue seasoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasoningType Context triple: [Kettle Brand Backyard Barbeque potato chips, seasoningType, barbecue seasoning]
-
A.
seasoningStyle
Indicates the characteristic way in which an item is flavored or seasoned, such as the method, intensity, or cultural style of its seasoning.
-
B.
sauceType
Indicates the specific kind or category of sauce associated with an item or dish.
-
C.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
D.
typicalSpices
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
-
E.
isSavory
Indicates that something has a salty, spicy, or umami-dominant taste rather than a sweet one.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65806ea888190850421154238d91c |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.