Triple
T6708761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbaresco |
E153074
|
entity |
| Predicate | traditionalFoodPairings |
P14740
|
FINISHED |
| Object | truffle dishes |
—
|
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: truffle dishes | Statement: [Barbaresco, traditionalFoodPairings, truffle dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFoodPairings Context triple: [Barbaresco, traditionalFoodPairings, truffle dishes]
-
A.
typicalFoodPairing
chosen
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
B.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
C.
traditionalCuisine
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
D.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
E.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.