Triple
T1702632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Independence Day |
E36800
|
entity |
| Predicate | foodAssociated |
P7171
|
FINISHED |
| Object | chiles en nogada |
—
|
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: chiles en nogada | Statement: [Mexican Independence Day, foodAssociated, chiles en nogada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodAssociated Context triple: [Mexican Independence Day, foodAssociated, chiles en nogada]
-
A.
foodCustom
chosen
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
B.
favoriteFood
Indicates that one entity has a preferred or most liked food item in relation to another entity or context.
-
C.
typicalFoodPairing
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
D.
foodSources
Indicates a relationship where one entity serves as a source of food or nourishment for another entity.
-
E.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab75ad24408190814069e6e3ef9e59 |
completed | March 7, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69aa61bad17c8190861b92cfb423f68f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.