Triple
T30618691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Custis II |
E779383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial Virginia planter |
C3697
|
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: colonial Virginia planter Context triple: [John Custis II, instanceOf, colonial Virginia planter]
-
A.
colonial Virginia family
A colonial Virginia family is a kinship-based household unit in 17th–18th century Virginia, typically headed by a white male landowner, encompassing spouse, children, extended relatives, enslaved people, and sometimes indentured servants, all embedded in a plantation-based, hierarchical social and economic structure.
-
B.
colonial-era plantation
A colonial-era plantation is a large agricultural estate established during the colonial period that relied on coerced or enslaved labor to produce cash crops for export, typically reinforcing systems of racial and economic exploitation.
-
C.
colonial proprietor
A colonial proprietor is an individual or entity granted ownership and governing rights over a colony by a sovereign power, responsible for its administration, development, and profit.
-
D.
plantation owner
chosen
A plantation owner is an individual who possesses and manages a large agricultural estate, historically relying on coerced or enslaved labor to cultivate cash crops for profit.
-
E.
Virginia aristocrat
A Virginia aristocrat is a member of the historically wealthy, landowning elite of Virginia, characterized by inherited social status, political influence, and a lifestyle rooted in plantation culture and tradition.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.