Triple
T5036569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leicester House, London |
E113437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aristocratic residence |
C14382
|
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: aristocratic residence Context triple: [Leicester House, London, instanceOf, aristocratic residence]
-
A.
former royal residence
A former royal residence is a historic building or estate that once served as an official home for a monarch or royal family but no longer functions in that capacity.
-
B.
residential palace building
chosen
A residential palace building is a grand, often historically or culturally significant dwelling designed to house royalty, nobility, or other high-status residents, featuring luxurious architecture, expansive interiors, and formal reception spaces.
-
C.
Renaissance palace
A Renaissance palace is a grand urban residence characterized by symmetrical facades, classical orders, and richly decorated interiors that reflect the humanist ideals and artistic innovations of the Renaissance period.
-
D.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
E.
Baroque palace
A Baroque palace is a grand, ornately decorated residence characterized by dramatic architecture, elaborate ornamentation, and richly detailed interiors designed to display power and opulence.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.