Triple
T20546248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bull’s Head, Mobberley |
E504476
|
entity |
| Predicate | styleOfCuisine |
P5786
|
FINISHED |
| Object | traditional pub fare |
—
|
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: traditional pub fare | Statement: [The Bull’s Head, Mobberley, styleOfCuisine, traditional pub fare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfCuisine Context triple: [The Bull’s Head, Mobberley, styleOfCuisine, traditional pub fare]
-
A.
foodPreparationStyle
Indicates the manner or method by which food is prepared, cooked, or processed.
-
B.
cuisineType
chosen
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
C.
cuisineSubtype
Indicates that one cuisine is a more specific subtype or variant within the broader category of another cuisine.
-
D.
diningStyle
Indicates the manner or format in which dining is conducted, such as casual, formal, buffet, or family-style.
-
E.
genreOfRecipes
Indicates that one entity is a genre or category that characterizes the type or style of recipes associated with another entity.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a298630c8190993d53fc27eb3aec |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.