Triple
T25791212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowcountry cuisine |
E649552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern United States cuisine |
C41734
|
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: Southern United States cuisine Context triple: [Lowcountry cuisine, instanceOf, Southern United States cuisine]
-
A.
Southern restaurant
A Southern restaurant is a dining establishment that specializes in traditional cuisine from the Southern United States, often featuring dishes like fried chicken, barbecue, biscuits, and collard greens in a warm, hospitable setting.
-
B.
Tex-Mex cuisine
Tex-Mex cuisine is a regional American style of cooking that blends Mexican culinary traditions with Texan ingredients and techniques, featuring dishes like chili con carne, fajitas, and nachos with generous use of cheese, beef, and spices.
-
C.
American food
chosen
American food is a diverse and evolving cuisine that blends Indigenous, European, African, Asian, and Latin American influences into regional and national dishes such as burgers, barbecue, fried chicken, and Tex-Mex.
-
D.
Southern planter family
A Southern planter family is a wealthy, landowning household in the American South whose social status, economic power, and cultural identity are rooted in the ownership and management of large agricultural estates, historically reliant on enslaved labor.
-
E.
New England cuisine
New England cuisine is a regional American cooking tradition characterized by simple, hearty dishes that highlight local seafood, dairy, and seasonal produce, often influenced by colonial and maritime heritage.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:59 a.m.