Triple
T8593606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-sphere Integrated Plan |
E203489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese Communist Party policy concept |
C2589
|
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: Chinese Communist Party policy concept Context triple: [Five-sphere Integrated Plan, instanceOf, Chinese Communist Party policy concept]
-
A.
Chinese communist
A Chinese communist is an individual who supports or adheres to the principles, ideology, and political program of the Communist Party of China within the context of the Chinese socialist system.
-
B.
political concept
chosen
A political concept is an abstract idea or principle used to understand, analyze, and organize power relations, governance structures, and public decision-making within societies.
-
C.
Chinese political figure
A Chinese political figure is an individual who holds or has held a position of political authority or influence within the governmental or party structures of the People’s Republic of China or its predecessor regimes.
-
D.
Chinese imperial policy
Chinese imperial policy refers to the evolving set of centralized governance strategies, legal codes, bureaucratic institutions, and ideological doctrines—especially Confucianism—used by successive dynasties to maintain authority, manage society, and regulate relations with neighboring states.
-
E.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.