Triple
T28499837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunnan rice noodles |
E721202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional specialty of Yunnan |
C13146
|
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: regional specialty of Yunnan Context triple: [Yunnan rice noodles, instanceOf, regional specialty of Yunnan]
-
A.
regional specialty
chosen
A regional specialty is a product, dish, or craft uniquely associated with and characteristic of a specific geographic area, reflecting its local culture, resources, and traditions.
-
B.
Sichuan cuisine ingredient
A Sichuan cuisine ingredient is any food component—such as chili peppers, Sichuan peppercorns, fermented bean pastes, aromatics, or pickled vegetables—used to create the region’s characteristic bold, spicy, and numbing flavors.
-
C.
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.
-
D.
Southern Min variety
A Southern Min variety is a regional form of the Southern Min (Minnan) branch of Chinese, encompassing mutually related but often not mutually intelligible dialects spoken primarily in southern Fujian, eastern Guangdong, Hainan, Taiwan, and among overseas Chinese communities.
-
E.
Chinese regional cuisine
Chinese regional cuisine encompasses the diverse, locality-specific culinary traditions of China, each defined by unique ingredients, techniques, and flavor profiles shaped by geography, climate, and culture.
- F. None of above.
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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:06 a.m.