Triple
T21193490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningrad City Committee of the Communist Party |
E522266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local party authority |
C1677
|
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: local party authority Context triple: [Leningrad City Committee of the Communist Party, instanceOf, local party authority]
-
A.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
B.
one‑party state authority
chosen
A one-party state authority is a governing body in which a single political party monopolizes political power, controls state institutions, and suppresses or severely restricts opposition.
-
C.
local council
A local council is a governing body elected or appointed to make decisions, set policies, and manage public services for a specific municipality or local area.
-
D.
local government meeting
A local government meeting is a formal gathering where elected officials, staff, and sometimes community members convene to discuss, deliberate, and make decisions on public policies, services, and issues affecting a specific municipality or region.
-
E.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.