Triple
T23760167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet and Sour Carp |
E587227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shandong cuisine dish |
C48024
|
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: Shandong cuisine dish Context triple: [Sweet and Sour Carp, instanceOf, Shandong cuisine dish]
-
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.
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.
-
C.
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.
-
D.
Korean noodle dish
A Korean noodle dish is a traditional or modern Korean meal centered around noodles, typically served in hot broth, stir-fried, or chilled with various toppings, sauces, and seasonings.
-
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. 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:14 p.m.