Triple
T23947273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston, Plymouth Colony |
E602948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era settlement |
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: colonial-era settlement Context triple: [Kingston, Plymouth Colony, instanceOf, colonial-era settlement]
-
A.
former colonial settlement
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
-
B.
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.
-
C.
colonial-era plantation
A colonial-era plantation is a large agricultural estate established during the colonial period that relied on coerced or enslaved labor to produce cash crops for export, typically reinforcing systems of racial and economic exploitation.
-
D.
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.
-
E.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:17 p.m.