Triple
T29952034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thoresby area of Nottinghamshire |
E760794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic country estate region |
C49172
|
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: historic country estate region Context triple: [Thoresby area of Nottinghamshire, instanceOf, historic country estate region]
-
A.
historic estate
A historic estate is a large, significant property—often including a grand residence, outbuildings, and landscaped grounds—that holds cultural, architectural, or historical importance from a past era.
-
B.
historic landed estates
chosen
Historic landed estates are large, traditionally inherited properties comprising extensive landholdings, grand residences, and associated economic, social, and cultural structures that reflect the power and legacy of longstanding landowning families or institutions.
-
C.
historic ruined country house
A historic ruined country house is a once-grand rural residence now partially or wholly decayed, whose surviving architecture and setting evoke its former status, period style, and the passage of time.
-
D.
former country estate
A former country estate is a large rural property that once served as the grand residential and agricultural domain of a wealthy owner, but has since been repurposed, subdivided, or fallen from its original status.
-
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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:26 p.m.