Triple
T19176888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pleasant, Westmoreland County, Colony of Virginia |
E469462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plantation estate |
C1853
|
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: plantation estate Context triple: [Mount Pleasant, Westmoreland County, Colony of Virginia, instanceOf, plantation estate]
-
A.
colonial estate
A colonial estate is a large property established during a colonial period, typically featuring expansive landholdings, a grand main residence, and outbuildings used for agriculture, administration, and housing laborers.
-
B.
country estate
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.
-
C.
plantation
chosen
A plantation is a large-scale agricultural estate, typically in tropical or subtropical regions, where a single cash crop is intensively cultivated, often historically associated with coerced or enslaved labor.
-
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.
Hudson River estate
A Hudson River estate is a grand, often historic country property situated along New York’s Hudson River, typically featuring expansive grounds, scenic river views, and architecturally significant residences.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:07 p.m.