Triple
T4584643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian colonization of the Americas |
E101938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian overseas expansion |
C2572
|
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 overseas expansion Context triple: [Russian colonization of the Americas, instanceOf, Russian overseas expansion]
-
A.
Greek expansion
Greek expansion refers to the historical process by which Greek culture, language, political influence, and settlements spread beyond the Greek mainland into the wider Mediterranean and Near Eastern regions through colonization, conquest, and trade.
-
B.
Russian naval expedition
A Russian naval expedition is a state-organized maritime operation undertaken by the Russian Navy for purposes such as exploration, power projection, military engagement, or strategic presence beyond home waters.
-
C.
Russian-style colony
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.
-
D.
territorial acquisition
chosen
Territorial acquisition is the process by which a state or entity gains control over land or geographic space through means such as conquest, cession, purchase, occupation, or accretion.
-
E.
expansionist doctrine
An expansionist doctrine is a belief system or policy framework that justifies and promotes the territorial, economic, or political enlargement of a state or group, often at the expense of others.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:10 p.m.