Triple
T28494598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Hill, Cherokee Nation |
E721072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic Cherokee community |
C54129
|
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: historic Cherokee community Context triple: [Park Hill, Cherokee Nation, instanceOf, historic Cherokee community]
-
A.
historic tribe
A historic tribe is a distinct social and cultural group from the past, typically defined by shared ancestry, traditions, language, and territory, whose identity and way of life are documented in historical records.
-
B.
Overhill Cherokee town
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.
-
C.
Lenape community
A Lenape community is a group of people connected by Lenape ancestry, culture, language, and traditions, often organized around shared land, governance, and cultural practices.
-
D.
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.
-
E.
Cocopah community
The Cocopah community is a Native American group centered along the lower Colorado River, maintaining a distinct cultural identity through traditional practices, language, and governance while engaging with surrounding regional societies.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:03 a.m.