Triple
T19381401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettle Brand Organic potato chips |
E484817
|
entity |
| Predicate | hasIngredientType |
P40800
|
FINISHED |
| Object | potatoes |
—
|
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: potatoes | Statement: [Kettle Brand Organic potato chips, hasIngredientType, potatoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIngredientType Context triple: [Kettle Brand Organic potato chips, hasIngredientType, potatoes]
-
A.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
hasDishType
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
C.
ingredientType
chosen
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
D.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a6075a88190aed7afa3b8fd3021 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.