Triple
T2210519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamb House, Rye, East Sussex |
E50905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian townhouse |
C5702
|
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 townhouse Context triple: [Lamb House, Rye, East Sussex, instanceOf, Georgian townhouse]
-
A.
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.
-
B.
Historic house
chosen
A historic house is a residential building recognized for its significant architectural, cultural, or historical value, often preserved or restored to reflect the period in which it was built.
-
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.
Newport mansion
A Newport mansion is a grand, historically significant seaside estate in Newport, Rhode Island, known for its opulent architecture, lavish interiors, and association with America’s Gilded Age elite.
-
E.
historic estate type
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.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.