Triple
T35994746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland settlements |
E1040949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early American frontier communities |
C26555
|
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: early American frontier communities Context triple: [Cumberland settlements, instanceOf, early American frontier communities]
-
A.
frontier communities
chosen
Frontier communities are small, often isolated settlements located at the edge of established territories, characterized by limited infrastructure, close-knit social ties, and a strong reliance on local resources and self-sufficiency.
-
B.
pioneer movement
The pioneer movement is a historical and social phenomenon in which individuals or groups venture into new, often remote territories to settle, develop resources, and establish communities, driving expansion and cultural change.
-
C.
historic Cherokee community
A historic Cherokee community is a traditional settlement or locale where Cherokee people lived and maintained their social, political, and cultural practices during a specific period in the past.
-
D.
frontier militia
A frontier militia is a locally organized, often semi-formal armed group formed by settlers or border communities to defend remote or contested territories from external threats and maintain basic security.
-
E.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.