Triple
T12627346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yan'an Rectification Movement |
E301548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intra-party rectification movement |
C26052
|
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: intra-party rectification movement Context triple: [Yan'an Rectification Movement, instanceOf, intra-party rectification movement]
-
A.
division of the Chinese Communist Party
A division of the Chinese Communist Party is an organizational unit within the Party’s hierarchical structure responsible for implementing Party policies, managing members, and coordinating political activities in a specific sector, region, or institution.
-
B.
centralization reform
Centralization reform is a process of restructuring governance or organizational systems to concentrate decision-making authority, resources, and control within a central body or leadership.
-
C.
organizational reform
chosen
Organizational reform is the deliberate process of redesigning an organization’s structures, processes, and cultures to improve effectiveness, adapt to changing environments, and better achieve strategic goals.
-
D.
revolutionary committee
A revolutionary committee is a temporary governing or coordinating body formed during a revolution to organize, direct, and implement political, military, or social change against an existing regime.
-
E.
Communist Party resolution
A Communist Party resolution is a formal, collectively adopted document that articulates the party’s official position, policies, or strategic directives on specific political, ideological, or organizational issues.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:14 p.m.