Triple
T13025113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Andrés Mixquic |
E326283
|
entity |
| Predicate | usesTraditionalFood |
P19483
|
FINISHED |
| Object | tamales |
—
|
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: tamales | Statement: [San Andrés Mixquic, usesTraditionalFood, tamales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalFood Context triple: [San Andrés Mixquic, usesTraditionalFood, tamales]
-
A.
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.
-
B.
traditionalFoodBase
Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with another entity.
-
C.
traditionalDish
chosen
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
D.
servesTradition
Indicates that one entity upholds, maintains, or performs a tradition for the benefit or continuation of that tradition.
-
E.
traditionallyServed
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with another entity.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:53 p.m.