Triple
T14566460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litbel |
E341797
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | client state of Soviet Russia |
C857
|
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: client state of Soviet Russia Context triple: [Litbel, instanceOf, client state of Soviet Russia]
-
A.
client state
chosen
A client state is a country that is formally independent but heavily influenced or controlled politically, economically, or militarily by a more powerful state.
-
B.
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.
-
C.
client state of the Roman Republic
A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
-
D.
state body of the Russian Federation
A state body of the Russian Federation is an official public authority established by the Constitution or federal law, empowered to exercise legislative, executive, or judicial functions within the Russian state system.
-
E.
client state of the Habsburg monarchy
A client state of the Habsburg monarchy was a formally separate polity whose government, foreign policy, or succession was effectively controlled or heavily influenced by the Habsburgs, serving their strategic, dynastic, or military interests.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.