Triple
T3266254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian–Belorussian Soviet Socialist Republic |
E68534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet puppet state |
C11282
|
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 puppet state Context triple: [Lithuanian–Belorussian Soviet Socialist Republic, instanceOf, Soviet puppet state]
-
A.
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.
-
B.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
C.
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.
-
D.
socialist republic
chosen
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.
-
E.
totalitarian state
A totalitarian state is a political system in which a centralized authority seeks to control all aspects of public and private life, suppressing opposition and individual freedoms through pervasive surveillance, propaganda, and coercion.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:09 p.m.