Triple
T20187433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Flower Spaghetti & Meatballs |
E492898
|
entity |
| Predicate | partOfMenu |
P61811
|
FINISHED |
| Object | Toadstool Cafe menu |
—
|
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: Toadstool Cafe menu | Statement: [Fire Flower Spaghetti & Meatballs, partOfMenu, Toadstool Cafe menu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfMenu Context triple: [Fire Flower Spaghetti & Meatballs, partOfMenu, Toadstool Cafe menu]
-
A.
menuItemType
Indicates the relationship between a menu item and the type or category it belongs to (e.g., appetizer, main course, dessert).
-
B.
menuType
Indicates the classification or category of a menu (e.g., main menu, context menu, settings menu) associated with an interface or system.
-
C.
servesPartOf
Indicates that one entity functions as a service or provider that operates within, or as a component of, another larger system or context.
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
menuCategory
chosen
Indicates the classification relationship that assigns an item to a specific section or category within a menu.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad2c43c8190a2fc5ef2a0514e53 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.