Triple
T28992061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Russia |
E736051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former territory of the Russian Empire |
C24568
|
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: former territory of the Russian Empire Context triple: [New Russia, instanceOf, former territory of the Russian Empire]
-
A.
former subdivision of the Russian Empire
chosen
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.
-
B.
constituent entity of Russia
A constituent entity of Russia is a primary administrative-territorial unit of the Russian Federation, such as a republic, krai, oblast, city of federal significance, autonomous okrug, or autonomous oblast, that possesses a defined degree of political and administrative autonomy under federal law.
-
C.
constituent republic of the Soviet Union
A constituent republic of the Soviet Union was a nominally sovereign national republic that, while having its own government and constitution, was politically and economically subordinate to the central Soviet federal authority.
-
D.
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.
-
E.
former territory of Poland
A former territory of Poland is a geographic area that was once under Polish sovereignty or administration but is no longer part of the modern Polish state.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:26 a.m.