Triple
T12517963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Ciudad del Chicharrón |
E299237
|
entity |
| Predicate | associatedWithDish |
P79219
|
FINISHED |
| Object | pork-based 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: pork-based dishes | Statement: [La Ciudad del Chicharrón, associatedWithDish, pork-based dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDish Context triple: [La Ciudad del Chicharrón, associatedWithDish, pork-based dishes]
-
A.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
B.
knownForDish
chosen
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
hasDishType
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
E.
alsoSitsWith
Indicates that one entity sits together with another entity, sharing the same seating context or location.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.