Triple
T29915881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantonese ginger milk curd |
E759794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cantonese dessert |
C56531
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Cantonese dessert Context triple: [Cantonese ginger milk curd, instanceOf, Cantonese dessert]
-
A.
Cantonese-speaking region
A Cantonese-speaking region is a geographic area where Cantonese is widely used as a primary language in daily life, culture, media, and local institutions.
-
B.
Huizhou Chinese variety
Huizhou Chinese variety is a group of closely related Sinitic lects spoken in southern Anhui and nearby regions, characterized by significant phonological and lexical divergence from Mandarin and other major Chinese varieties.
-
C.
Chinese cold dish
A Chinese cold dish is a chilled appetizer or side dish featuring ingredients like vegetables, meats, tofu, or noodles, typically seasoned with soy sauce, vinegar, chili oil, garlic, and aromatic spices to create refreshing and flavorful combinations.
-
D.
Chaoshan cuisine dish
A Chaoshan cuisine dish is a traditional food item from the Chaoshan region of Guangdong, China, characterized by delicate flavors, emphasis on fresh seafood and slow-cooked broths, and often accompanied by distinctive sauces and condiments.
-
E.
Taiwanese noodle dish
A Taiwanese noodle dish is a savory preparation featuring noodles served in broth or stir-fried, typically accompanied by regional toppings such as braised meats, seafood, vegetables, and aromatic seasonings that reflect Taiwan’s diverse culinary influences.
- F. None of above. chosen
Provenance (1 batch)
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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:12 p.m.