Triple
T10042624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongyuan Pianzheng |
E205332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese historical event |
C27335
|
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 historical event Context triple: [Zhongyuan Pianzheng, instanceOf, Chinese historical event]
-
A.
Japanese historical event
A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
-
B.
revolutionary event in China
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.
-
C.
era in Chinese history
An era in Chinese history is a distinct period marked by characteristic political structures, cultural developments, social changes, and significant events that differentiate it from other historical periods in China.
-
D.
Chinese historical novel
A Chinese historical novel is a long-form narrative that dramatizes events, figures, and social conditions from China’s past, blending historical fact with literary imagination to explore cultural, political, and moral themes.
-
E.
Chinese Civil War battle
A Chinese Civil War battle is an armed conflict between opposing Chinese political and military factions, primarily the Nationalists and Communists, fought between 1927 and 1950 as part of the struggle for control of China.
- F. None of above. chosen
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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.