Triple
T28494229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanasi |
E721060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic Cherokee town |
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: historic Cherokee town Context triple: [Tanasi, instanceOf, historic Cherokee town]
-
A.
historic townsite
A historic townsite is a preserved area of an earlier settlement that retains significant buildings, structures, and spatial layout reflecting its historical, cultural, or architectural importance.
-
B.
historic town
A historic town is a settlement characterized by preserved architecture, landmarks, and cultural features that reflect significant events, periods, or traditions from the past.
-
C.
historic township
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
D.
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.
-
E.
historic camp
A historic camp is a preserved or commemorated site where people once lived, trained, or gathered temporarily, now recognized for its cultural, social, or historical significance.
- 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.