Triple
T18786243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenies Manor House |
E459383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor manor house |
C41227
|
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: Tudor manor house Context triple: [Chenies Manor House, instanceOf, Tudor manor house]
-
A.
Elizabethan manor house
An Elizabethan manor house is a grand, often symmetrical country residence from late 16th- to early 17th-century England, characterized by its ornate gables, large mullioned windows, and richly decorated interiors reflecting the wealth and status of its owners.
-
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.
medieval mansion
A medieval mansion is a large, fortified residence of nobility featuring stone construction, great halls, defensive elements, and expansive grounds reflecting wealth and social status in the Middle Ages.
-
D.
manorial estate
A manorial estate is a large landed property in medieval and early modern Europe comprising the lord’s residence, peasant holdings, and common resources, organized as a self-sufficient economic and social unit under feudal control.
-
E.
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.
- F. None of above. chosen
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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.