Triple
T23703183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portman Estate |
E585648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | privately owned estate |
C2435
|
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: privately owned estate Context triple: [Portman Estate, instanceOf, privately owned estate]
-
A.
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.
-
B.
privately managed park
A privately managed park is a recreational green space owned or operated by a non-governmental entity that controls access, maintenance, and permitted activities, often funded through fees, memberships, or private investment.
-
C.
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.
-
D.
country estate
chosen
A country estate is a large, often historic rural property that typically includes a grand residence, extensive grounds, and associated outbuildings used for agriculture, leisure, or both.
-
E.
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.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:53 p.m.