Triple
T10665764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian military fort of Verny |
E251353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tsarist frontier outpost |
C11307
|
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: Tsarist frontier outpost Context triple: [Russian military fort of Verny, instanceOf, Tsarist frontier outpost]
-
A.
Cossack territory
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
-
B.
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.
-
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.
frontier post
chosen
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
-
E.
Genoese colony
A Genoese colony was a territorial possession or trading outpost established and administered by the Republic of Genoa to control maritime commerce, strategic ports, and regional influence across the Mediterranean and Black Sea.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:08 p.m.