Triple
T18601724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodiak settlement |
E454635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian colonial settlement |
C13188
|
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: Russian colonial settlement Context triple: [Kodiak settlement, instanceOf, Russian colonial settlement]
-
A.
Russian-style colony
chosen
A Russian-style colony is a settlement or territory established and controlled by Russia that reflects Russian governance, culture, language, and economic interests, often emphasizing centralized authority and strategic or resource-based exploitation.
-
B.
Russian-American
A Russian-American is an individual of Russian origin or descent who resides in, identifies with, or holds citizenship in the United States, blending aspects of Russian and American cultures.
-
C.
English colonial settlement
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.
-
D.
Spanish colonial settlement
A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
-
E.
Arctic settlement
An Arctic settlement is a small, often remote community located within the Arctic region, adapted to extreme cold, seasonal darkness, and fragile polar ecosystems while supporting human habitation and local economic activities.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.