Triple
T14175618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Tang at The Dorchester |
E351324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cantonese restaurant |
C9570
|
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 restaurant Context triple: [China Tang at The Dorchester, instanceOf, Cantonese restaurant]
-
A.
Chinese restaurant
chosen
A Chinese restaurant is a dining establishment that specializes in preparing and serving Chinese cuisine, often featuring regional dishes, traditional cooking techniques, and culturally themed decor.
-
B.
Thai restaurant
A Thai restaurant is a dining establishment that specializes in serving traditional and contemporary Thai cuisine, often featuring bold flavors, aromatic herbs, and a balance of sweet, sour, salty, and spicy dishes.
-
C.
Japanese restaurant
A Japanese restaurant is a dining establishment that specializes in preparing and serving traditional and contemporary Japanese cuisine, such as sushi, sashimi, ramen, tempura, and bento, often emphasizing fresh ingredients, seasonal dishes, and meticulous presentation.
-
D.
teppanyaki restaurant
A teppanyaki restaurant is a dining establishment where chefs cook and theatrically prepare Japanese-style grilled dishes on a large iron griddle in front of guests.
-
E.
Mexican restaurant
A Mexican restaurant is a dining establishment that specializes in preparing and serving traditional and contemporary Mexican cuisine, often featuring dishes like tacos, enchiladas, and burritos, along with characteristic flavors such as chili, lime, and cilantro.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:02 a.m.