Triple
T36577554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parque de Santa Ana |
E902296
|
entity |
| Predicate | typicalDishSold |
P102737
|
FINISHED |
| Object | cochinita pibil |
—
|
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: cochinita pibil | Statement: [Parque de Santa Ana, typicalDishSold, cochinita pibil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDishSold Context triple: [Parque de Santa Ana, typicalDishSold, cochinita pibil]
-
A.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
B.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
C.
foodSold
chosen
Indicates that a particular food item is sold or offered for sale by a specific seller or at a specific place.
-
D.
isTypicallyServedIn
Indicates that something (such as a food or drink) is most commonly or customarily presented or contained within a particular type of vessel or container.
-
E.
isTypicallyEatenWith
Indicates that one item is commonly consumed together with another as part of the same eating occasion 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.