Triple
T1850954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yachtsman Steakhouse |
E41391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | upscale dining establishment |
C2014
|
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: upscale dining establishment Context triple: [Yachtsman Steakhouse, instanceOf, upscale dining establishment]
-
A.
fine-dining restaurant
chosen
A fine-dining restaurant is an upscale establishment that offers meticulously prepared gourmet cuisine, refined service, and an elegant atmosphere, often with a focus on high-quality ingredients and an extensive wine list.
-
B.
gourmet restaurant
A gourmet restaurant is a high-end dining establishment that offers meticulously prepared, artistically presented dishes made from premium ingredients, often accompanied by exceptional service and an extensive wine selection.
-
C.
casual dining restaurant
A casual dining restaurant is a moderately priced, full-service eatery offering a relaxed atmosphere, table service, and a varied menu of familiar, comfort-oriented dishes.
-
D.
on-campus dining venue
An on-campus dining venue is a food service location situated within a college or university that provides meals, snacks, and beverages to students, faculty, staff, and visitors, often accepting campus meal plans and offering spaces for socializing or studying.
-
E.
revolving restaurant
A revolving restaurant is a dining establishment, typically located atop a tall building or structure, whose seating area slowly rotates to provide guests with a 360-degree panoramic view while they eat.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.