Triple
T21149602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningrad Regional Soviet |
E521151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional soviet |
C21157
|
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: regional soviet Context triple: [Leningrad Regional Soviet, instanceOf, regional soviet]
-
A.
regional legislature of Russia
A regional legislature of Russia is a representative elected body at the subnational (federal subject) level that enacts laws, approves budgets, and oversees executive authorities within its respective region in accordance with the Russian Federation’s constitutional framework.
-
B.
regional committee of a communist party
A regional committee of a communist party is a territorial governing body responsible for implementing party policies, coordinating local organizations, and directing political, organizational, and ideological work within a specific geographic area.
-
C.
regional assembly
chosen
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
-
D.
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.
-
E.
district of Russia
A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.