Triple
T26664441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opechancanough |
E672141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Powhatan person |
C8359
|
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: Powhatan person Context triple: [Opechancanough, instanceOf, Powhatan person]
-
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.
member of the Powhatan people
chosen
A member of the Powhatan people is an individual belonging to the Indigenous Algonquian-speaking tribal nations historically inhabiting the Tidewater region of present-day Virginia, known for their complex chiefdom, agricultural practices, and interactions with early English colonists.
-
C.
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.
-
D.
Lenape person
A Lenape person is an individual belonging to the Lenape (Delaware) Indigenous people, whose identity is rooted in their ancestral homelands, cultural traditions, and community ties.
-
E.
Patuxet person
A Patuxet person is an individual belonging to the Patuxet people, an Indigenous group of the Wampanoag confederation who historically lived in what is now Plymouth, Massachusetts, prior to and during early English colonization.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:08 a.m.