Triple
T25644858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goubuli |
E642931
|
entity |
| Predicate | hasMainDishType |
P84496
|
FINISHED |
| Object | meat-filled buns |
—
|
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: meat-filled buns | Statement: [Goubuli, hasMainDishType, meat-filled buns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainDishType Context triple: [Goubuli, hasMainDishType, meat-filled buns]
-
A.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
hasDishType
chosen
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.
isMainCourse
Indicates that an item functions as the primary or central dish within a meal, rather than a side, appetizer, or dessert.
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 21, 2026, 5:50 p.m.