Triple
T15390388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goring House (on or near the site) |
E368028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London mansion |
C29890
|
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: London mansion Context triple: [Goring House (on or near the site), instanceOf, London mansion]
-
A.
townhouse in London
chosen
A townhouse in London is a multi-story, typically narrow urban residence sharing side walls with neighboring homes, often featuring period architecture and situated along a city street or terrace.
-
B.
Soho House property
A Soho House property is a members-only, design-led club and accommodation space that offers curated hospitality, work, dining, and social experiences tailored primarily to creative professionals.
-
C.
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.
-
D.
Tudor palace
A Tudor palace is a grand, often asymmetrical royal or noble residence from England’s Tudor period, characterized by red-brick construction, ornate chimneys, timber framing, and richly decorated interiors reflecting both medieval and early Renaissance influences.
-
E.
aristocratic mansion
An aristocratic mansion is a grand, opulent residence historically owned by nobility or the elite, characterized by expansive grounds, elaborate architecture, and richly decorated interiors that symbolize wealth, power, and social status.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.