Triple
T14352989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipropetrovsk Regional Committee of the Communist Party of Ukraine |
E355900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | party regional committee |
C20244
|
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: party regional committee Context triple: [Dnipropetrovsk Regional Committee of the Communist Party of Ukraine, instanceOf, party regional committee]
-
A.
party executive committee
The party executive committee is the central leadership body of a political party responsible for making strategic decisions, setting policy directions, and overseeing organizational operations.
-
B.
party caucus
A party caucus is a meeting of members of a political party or faction to coordinate strategy, select leaders or candidates, and decide on policy positions.
-
C.
subnational party leadership body
chosen
A subnational party leadership body is an organized group of party officials at a regional, state, or local level responsible for directing party strategy, coordinating activities, and representing the party within that specific territorial jurisdiction.
-
D.
party secretariat
The party secretariat is the organizational body within a political party responsible for managing its day-to-day administration, implementing decisions of the leadership, and coordinating communication and activities across its structures.
-
E.
regional assembly
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.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:14 a.m.