Triple
T1005225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry Hill House |
E21693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic Revival villa |
C2541
|
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: Gothic Revival villa Context triple: [Strawberry Hill House, instanceOf, Gothic Revival villa]
-
A.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
-
B.
fortified manor house
A fortified manor house is a residential estate that combines the domestic functions of a manor with defensive features such as walls, towers, and gatehouses to protect its inhabitants.
-
C.
18th-century residence
An 18th-century residence is a dwelling built or styled in the architectural traditions of the 1700s, typically featuring symmetrical facades, period-appropriate materials, and interior layouts reflecting the social and domestic norms of the era.
-
D.
historic estate type
chosen
A historic estate type is a classification of large, historically significant residential properties characterized by their architectural style, period of construction, original function, and cultural or social importance.
-
E.
Georgian church building
A Georgian church building is a Christian place of worship constructed or used during the Georgian era (1714–1830/37), typically characterized by balanced classical proportions, restrained ornamentation, and often brick or stone facades reflecting the architectural tastes of that 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.