Triple
T19340823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin House (Cincinnati hotel) |
E483749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century hotel |
C2165
|
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: 19th-century hotel Context triple: [Franklin House (Cincinnati hotel), instanceOf, 19th-century hotel]
-
A.
19th-century residence
A 19th-century residence is a dwelling built or styled in the architectural traditions of the 1800s, typically featuring period-specific materials, ornamentation, and spatial layouts reflective of the social and technological context of that era.
-
B.
historic hotel
chosen
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.
-
C.
19th-century architectural project
A 19th-century architectural project is a planned building or complex designed and developed during the 1800s, reflecting the period’s characteristic styles, technologies, and cultural influences.
-
D.
19th-century restoration
19th-century restoration refers to the architectural and artistic practice of the 1800s that sought to repair, reconstruct, or stylistically unify historic buildings—often medieval—according to contemporary ideals of authenticity and aesthetics rather than strict historical accuracy.
-
E.
19th-century bridge
A 19th-century bridge is a transportation structure built during the 1800s that typically reflects the era’s industrial advances in materials and engineering, such as iron, steel, and improved masonry techniques.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.