Triple
T5193064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphis-style barbecue |
E117201
|
entity |
| Predicate | associatedDish |
P19483
|
FINISHED |
| Object | barbecue spaghetti |
—
|
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: barbecue spaghetti | Statement: [Memphis-style barbecue, associatedDish, barbecue spaghetti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDish Context triple: [Memphis-style barbecue, associatedDish, barbecue spaghetti]
-
A.
similarDish
Indicates that two dishes share notable similarities, such as ingredients, preparation methods, flavor profile, or style.
-
B.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
C.
typicalFoodPairing
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
D.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
E.
traditionalDish
chosen
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79efd16c8190b0b16278a00baecd |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.