Triple

T11871253
Position Surface form Disambiguated ID Type / Status
Subject Zunyi Conference, January 1935 E282411 entity
Predicate instanceOf P0 FINISHED
Object event in Chinese Communist Party history C15541 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: event in Chinese Communist Party history
Context triple: [Zunyi Conference, January 1935, instanceOf, event in Chinese Communist Party history]
  • A. revolutionary event in China chosen
    A revolutionary event in China is a significant historical occurrence involving organized collective action aimed at fundamentally transforming the country’s political, social, or economic structures.
  • B. 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.
  • C. event in the history of socialism
    An event in the history of socialism is a significant occurrence—such as a movement, policy, revolution, publication, or organizational milestone—that has notably influenced the development, practice, or perception of socialist ideas and institutions.
  • D. Chinese historical event
    A Chinese historical event is a significant occurrence in China’s past—such as a war, reform, revolution, treaty, or cultural milestone—that shaped the political, social, economic, or cultural development of Chinese civilization.
  • E. event in Myanmar history
    An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
  • 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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:43 p.m.