Triple
T26989084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choupette |
E679816
|
entity |
| Predicate | hasOwnDishes |
P161417
|
FINISHED |
| Object | Goyard and silver 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: Goyard and silver dishes | Statement: [Choupette, hasOwnDishes, Goyard and silver dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnDishes Context triple: [Choupette, hasOwnDishes, Goyard and silver dishes]
-
A.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
B.
hasSpecialtyFood
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
C.
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).
-
D.
hasStapleFood
Indicates that an entity’s primary or regularly consumed basic food item is another specified entity.
-
E.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218de4ec81908d3001e5b8748c7d |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:50 a.m.