Triple
T8358833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cupola House |
E196749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian-style residence |
C20568
|
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: Georgian-style residence Context triple: [Cupola House, instanceOf, Georgian-style residence]
-
A.
Georgian building
chosen
A Georgian building is a structure designed in the architectural style prevalent from the early 18th to early 19th centuries, characterized by symmetry, proportion, and classical details such as sash windows, decorative cornices, and brick or stone facades.
-
B.
Greek Revival building
A Greek Revival building is a structure designed in the early- to mid-19th-century architectural style that emulates classical Greek temples through features like tall columns, pediments, symmetrical facades, and bold, simple moldings.
-
C.
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.
-
D.
Federal-style townhouse
A Federal-style townhouse is a narrow, multi-story urban residence characterized by its symmetrical façade, refined brickwork, tall windows, and restrained classical detailing popular in the United States from roughly 1780 to 1830.
-
E.
Traditional house
A traditional house is a dwelling that reflects the architectural styles, materials, and construction methods characteristic of a particular culture or historical period.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:59 p.m.