Triple
T22441502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sichuan chili oil |
E554764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sichuan cuisine ingredient |
C46305
|
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: Sichuan cuisine ingredient Context triple: [Sichuan chili oil, instanceOf, Sichuan cuisine ingredient]
-
A.
Sichuan cuisine dish
A Sichuan cuisine dish is a Chinese regional specialty characterized by bold, complex flavors—especially numbing spiciness from Sichuan peppercorns and chili—often featuring stir-frying, braising, and liberal use of aromatics like garlic, ginger, and fermented sauces.
-
B.
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.
-
C.
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.
-
D.
stir-fry dish
A stir-fry dish is a quick-cooked meal made by tossing bite-sized ingredients in a small amount of hot oil over high heat, often seasoned with savory sauces and aromatics.
-
E.
Piedmontese dish
A Piedmontese dish is a traditional or contemporary food preparation originating from Italy’s Piedmont region, characterized by rich flavors, high-quality local ingredients, and often influenced by both rustic mountain and refined courtly culinary traditions.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:47 p.m.