Triple
T28494434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkeytown, Cherokee Nation |
E721067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cherokee settlement |
C24110
|
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: Cherokee settlement Context triple: [Turkeytown, Cherokee Nation, instanceOf, Cherokee settlement]
-
A.
Overhill Cherokee town
chosen
An Overhill Cherokee town was a principal 18th-century Cherokee settlement located along the upper Tennessee River and its tributaries, serving as a political, economic, and cultural center for the Overhill division of the Cherokee people.
-
B.
Muscogee tribal town
A Muscogee tribal town is a traditional socio-political and ceremonial community unit of the Muscogee (Creek) people, typically centered around a square ground and serving as a base for governance, ritual, and social life.
-
C.
Sauk settlement
A Sauk settlement is a community or village established and inhabited by the Sauk (Sac) people, typically organized around kinship networks, seasonal subsistence activities, and cultural practices in their traditional homelands.
-
D.
Cherokee
Cherokee: A Native American people originally from the southeastern United States, known for their rich cultural traditions, complex social and political structures, and resilience through forced removal and adaptation.
-
E.
Wampanoag village
A Wampanoag village is a semi-permanent Indigenous settlement composed of wetu (homes), communal work and gathering areas, and surrounding fields and woodlands that support the community’s seasonal subsistence and cultural life.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:03 a.m.