Triple
T31668847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bear Lake |
E808211
|
entity |
| Predicate | popularFoodAssociation |
P89569
|
FINISHED |
| Object | raspberry shakes |
—
|
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: raspberry shakes | Statement: [Bear Lake, popularFoodAssociation, raspberry shakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularFoodAssociation Context triple: [Bear Lake, popularFoodAssociation, raspberry shakes]
-
A.
favoriteFood
Indicates that one entity has a preferred or most liked food item in relation to another entity or context.
-
B.
foodRelatedMotif
Indicates a recurring theme, symbol, or pattern in which food plays a central role in the relationship or action between entities.
-
C.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
D.
foodCulture
chosen
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
-
E.
typicalFoodPairing
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 30, 2026, 11 p.m.