Triple
T15501894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Lynch |
E378979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founder of Lynchburg, Virginia |
C35554
|
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: founder of Lynchburg, Virginia Context triple: [John Lynch, instanceOf, founder of Lynchburg, Virginia]
-
A.
Powhatan
Powhatan is a conceptual class representing the leader of a powerful alliance of Algonquian-speaking tribes in 17th-century coastal Virginia, embodying indigenous political authority, diplomacy, and cultural identity during early English colonization.
-
B.
Count of Richmond
The Count of Richmond is a noble title historically associated with the English peerage, often granted to influential figures with territorial or honorary ties to the region of Richmond.
-
C.
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.
-
D.
Powhatan homeland
Powhatan homeland: The ancestral territory of the Powhatan people, encompassing the riverine coastal plains and woodlands of what is now eastern Virginia, where they lived, governed, and sustained their culture prior to and during early European colonization.
-
E.
governor of Virginia
The governor of Virginia is the elected chief executive of the Commonwealth, responsible for implementing state laws, overseeing the executive branch, and guiding public policy and the state budget.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:54 a.m.