Triple
T38639777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathauskeller (Hamburg) |
E938562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic cellar restaurant |
C7909
|
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: historic cellar restaurant Context triple: [Rathauskeller (Hamburg), instanceOf, historic cellar restaurant]
-
A.
historic restaurant
chosen
A historic restaurant is a long-established dining venue recognized for its significant cultural, architectural, or social heritage, often preserving traditional cuisine, decor, and stories from its past.
-
B.
historic chamber
A historic chamber is a formally recognized room or enclosed space of significant past events, architectural value, or cultural heritage, preserved or documented for its historical importance.
-
C.
historic barn
A historic barn is an old agricultural building of significant age and cultural, architectural, or historical value, often preserved as a heritage structure reflecting past farming practices and rural life.
-
D.
historic hotel
A historic hotel is a lodging establishment of notable age and preserved architectural or cultural significance that offers accommodations while reflecting the heritage of its era.
-
E.
historic boarding house
A historic boarding house is a long-standing residential building that once provided affordable, communal lodging—often with shared meals and services—to transient workers, travelers, or long-term tenants, reflecting the social and architectural character of its era.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.