Triple
T20891736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valpolicella |
E514422
|
entity |
| Predicate | traditionalFoodPairing |
P14740
|
FINISHED |
| Object | game 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: game dishes | Statement: [Valpolicella, traditionalFoodPairing, game dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFoodPairing Context triple: [Valpolicella, traditionalFoodPairing, game 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.
traditionalFoodBase
Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with another entity.
-
D.
foodInteraction
Indicates an interaction or relationship involving food between entities, such as consumption, sharing, preparation, or exchange.
-
E.
winePairing
Indicates a relationship where a particular wine is recommended as a suitable accompaniment for a given food or dish.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05f0bec8190a296db546bd34114 |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.