Triple
T15884108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshall family |
E385145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Virginia lineage |
C36610
|
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: Virginia lineage Context triple: [Marshall family, instanceOf, Virginia lineage]
-
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.
member of the Harrison family of Virginia
A member of the Harrison family of Virginia is an individual belonging to a prominent colonial and early American lineage known for its significant political, social, and economic influence in Virginia’s history.
-
C.
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.
-
D.
member of the Custis family
A member of the Custis family is an individual belonging by birth or legal relation to the historically prominent Custis lineage, known for its social, political, and economic influence in colonial and early American history.
-
E.
founder of Lynchburg, Virginia
The founder of Lynchburg, Virginia is the individual historically credited with establishing the original settlement that developed into the city of Lynchburg.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.