Triple
T33586890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Ministers of the Lithuanian SSR |
E860307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state organ of the Lithuanian SSR |
C43425
|
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: state organ of the Lithuanian SSR Context triple: [Council of Ministers of the Lithuanian SSR, instanceOf, state organ of the Lithuanian SSR]
-
A.
governing body of a Soviet republic
chosen
A governing body of a Soviet republic is the central political authority responsible for implementing Communist Party directives, managing state administration, and overseeing economic and social policy within that republic.
-
B.
organ of the Union State of Russia and Belarus
An organ of the Union State of Russia and Belarus is an official governing or administrative body established by the Union State to implement its joint policies, manage shared functions, and coordinate integration between the two member countries.
-
C.
governorate of the Russian SFSR
A governorate of the Russian SFSR was a primary administrative-territorial unit within the Russian Soviet Federative Socialist Republic, typically encompassing multiple districts and cities under a centralized regional government.
-
D.
region of Lithuania
A region of Lithuania is a defined territorial area within the country characterized by shared administrative, cultural, historical, or geographical features.
-
E.
county of Lithuania
A county of Lithuania is a top-level administrative division of the country that groups several municipalities for regional governance and statistical purposes.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.