Triple
T21518535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Towns of Connecticut |
E530908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early English settlements |
C213
|
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 English settlements Context triple: [River Towns of Connecticut, instanceOf, early English settlements]
-
A.
English colonial settlement
chosen
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
-
B.
Puritan settlement
A Puritan settlement is a religiously motivated colonial community organized around strict moral codes, communal labor, and governance rooted in Puritan interpretations of Christianity.
-
C.
Puritan migration
Puritan migration refers to the movement of English Puritans, primarily in the early 17th century, who left England to settle in North America and other regions in pursuit of religious freedom and the establishment of communities based on their strict Protestant beliefs.
-
D.
European colonists
European colonists were settlers from various European nations who migrated to and established control over foreign lands, often displacing indigenous populations and exploiting local resources for economic and political gain.
-
E.
historical settlement
A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:25 p.m.