Triple
T8757818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icy Blast |
E208116
|
entity |
| Predicate | hasKeyIngredientProfile |
P69349
|
FINISHED |
| Object | menthol cooling sensation |
—
|
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: menthol cooling sensation | Statement: [Icy Blast, hasKeyIngredientProfile, menthol cooling sensation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyIngredientProfile Context triple: [Icy Blast, hasKeyIngredientProfile, menthol cooling sensation]
-
A.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
C.
containsAllergenicCompound
Indicates that the subject entity includes one or more compounds known to cause allergic reactions.
-
D.
hasTastingProfile
chosen
Indicates that an entity possesses a specific flavor or sensory profile, typically describing its characteristic tastes and aromas.
-
E.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ddc2d9c81908948aee2b956cce4 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.