Triple
T6293818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Barbecue Festival |
E141081
|
entity |
| Predicate | hasFoodCategory |
P17971
|
FINISHED |
| Object | barbecue pork shoulders |
—
|
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 pork shoulders | Statement: [Lexington Barbecue Festival, hasFoodCategory, barbecue pork shoulders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoodCategory Context triple: [Lexington Barbecue Festival, hasFoodCategory, barbecue pork shoulders]
-
A.
hasFoodOption
Indicates that an entity offers, provides, or includes a particular type of food or dining option.
-
B.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
C.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
D.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
E.
hasMealType
Indicates that an entity is associated with a specific category or type of meal (such as breakfast, lunch, or dinner).
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06438654481908c9833c5f0d61773 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.