Triple
T33365073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarta de Mondoñedo |
E854329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish cuisine dish |
C59432
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Spanish cuisine dish Context triple: [Tarta de Mondoñedo, instanceOf, Spanish cuisine dish]
-
A.
Galician cuisine dish
chosen
A Galician cuisine dish is a traditional food preparation from the Galicia region of Spain, typically featuring local seafood, meats, potatoes, and greens, seasoned simply to highlight fresh, high-quality ingredients.
-
B.
Basque cuisine dish
A Basque cuisine dish is a prepared food item originating from the Basque Country that typically features local ingredients like seafood, peppers, and cod, and reflects the region’s distinctive culinary traditions and techniques.
-
C.
Spanish cuisine
Spanish cuisine is a diverse culinary tradition characterized by regional specialties that emphasize fresh, high-quality ingredients, olive oil, seafood, cured meats, and bold yet simple flavors often shared in small plates like tapas.
-
D.
traditional Basque dish
A traditional Basque dish is a regional preparation from the Basque Country that highlights local ingredients—especially seafood, peppers, and hearty stews—using time-honored cooking techniques and simple, robust flavors.
-
E.
Mexican dish
A Mexican dish is a prepared food item originating from Mexican cuisine, typically featuring ingredients like corn, beans, chili peppers, meats, cheeses, and vibrant seasonings, often served in combinations such as tacos, enchiladas, or tamales.
- F. None of above.
Provenance (1 batch)
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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.