Triple
T7647619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson family |
E173164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Virginia colonial dynasty |
C19724
|
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 colonial dynasty Context triple: [Jefferson family, instanceOf, Virginia colonial dynasty]
-
A.
Puritan dynasty
The Puritan dynasty is a conceptual class representing a ruling lineage or extended family whose governance, culture, and institutions are shaped by strict Puritan religious principles and moral codes.
-
B.
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.
-
C.
colonial-era Maryland family
A colonial-era Maryland family is a household unit living in Maryland between the 17th and late 18th centuries, typically characterized by patriarchal authority, agrarian or plantation-based livelihoods, reliance on enslaved or indentured labor, and strong ties to Anglican or other Protestant religious traditions.
-
D.
English colonial settlement
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
-
E.
member of the Harrison family of Virginia
chosen
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.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:58 p.m.