Triple
T22559102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Auditing Commission of the Workers' Party of Korea |
E557764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | party control organ |
C8132
|
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 control organ Context triple: [Central Auditing Commission of the Workers' Party of Korea, instanceOf, party control organ]
-
A.
party department
chosen
A party department is an organizational unit within a political party responsible for managing specific functions such as policy development, communications, membership, or campaign operations.
-
B.
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.
-
C.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
organ of the Assembly of the Republic
An organ of the Assembly of the Republic is an institutional body or structural component within the Assembly that performs specific legislative, administrative, or oversight functions to support its constitutional role.
-
E.
organ of the Senate of the Republic
An organ of the Senate of the Republic is an internal institutional body or structure within the Senate that performs specific legislative, administrative, or consultative functions to support its operation and decision-making.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:52 p.m.