Triple
T3194866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Ukraine |
E66911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet republic |
C1408
|
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: Soviet republic Context triple: [Soviet Ukraine, instanceOf, Soviet republic]
-
A.
constituent republic of the Soviet Union
chosen
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.
-
B.
republic of Russia
The Republic of Russia is a conceptual class representing a sovereign, federated state characterized by a republican form of government, centralized authority, and a diverse composition of regions and peoples within its political and legal framework.
-
C.
socialist republic
A socialist republic is a state governed as a republic in which political power and key means of production are formally organized and managed according to socialist principles, typically emphasizing public ownership, economic planning, and social welfare.
-
D.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union authority.
-
E.
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.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:07 p.m.