Triple
T30603280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reform and Opening-Up |
E778970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical period in China |
C11193
|
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: historical period in China Context triple: [Reform and Opening-Up, instanceOf, historical period in China]
-
A.
historical event in China
A historical event in China is a significant occurrence or series of occurrences within Chinese territory or involving Chinese society that has had a notable impact on the country's political, social, cultural, or economic development.
-
B.
era in Chinese history
chosen
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.
-
C.
historical province of China
A historical province of China is a former administrative region that once functioned as a distinct territorial unit under Chinese dynastic or early modern governments but has since been reorganized, renamed, or dissolved in later administrative reforms.
-
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.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:25 p.m.