Triple
T23271610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restaurant Gordon Ramsay |
E588304
|
entity |
| Predicate | hasTastingMenu |
P151627
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Restaurant Gordon Ramsay, hasTastingMenu, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTastingMenu Context triple: [Restaurant Gordon Ramsay, hasTastingMenu, yes]
-
A.
hasTastingRoom
Indicates that an establishment provides a dedicated space where visitors can sample or taste its products on-site.
-
B.
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).
-
C.
hasDiningOptionType
Indicates that an entity offers or is associated with a specific type or category of dining option (e.g., dine-in, takeout, delivery).
-
D.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
hasFoodOption
Indicates that an entity offers, provides, or includes a particular type of food or dining option.
- F. None of above. chosen
Provenance (4 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957418fc819085ee528622e0c6de |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:46 p.m.