Triple
T18446283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Empire in the Caucasus |
E450666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial frontier |
C19044
|
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: imperial frontier Context triple: [Russian Empire in the Caucasus, instanceOf, imperial frontier]
-
A.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
B.
Roman frontier
The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
-
C.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
D.
frontier province
chosen
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
E.
end of an empire
The end of an empire is the historical moment when a once-dominant imperial power irreversibly loses its political cohesion, territorial control, and cultural authority, giving way to new states, systems, or social orders.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.