Triple
T11014429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Alaska |
E260327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian colonial possession |
C5628
|
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 possession Context triple: [Russian Alaska, instanceOf, Russian colonial possession]
-
A.
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.
-
B.
Russian state
The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
-
C.
colonial territory
chosen
A colonial territory is a geographic area under the political control and administration of a distant foreign power, typically exploited for economic, strategic, or settlement purposes.
-
D.
former subdivision of the Russian Empire
A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
-
E.
state institution of the Russian Empire
A state institution of the Russian Empire was an official governmental body or administrative organ responsible for implementing imperial policies, managing public affairs, and exercising authority within the empire’s centralized bureaucratic system.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.