Triple
T15461658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Rites Controversy |
E371915
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty event |
C35476
|
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: Ming dynasty event Context triple: [Great Rites Controversy, instanceOf, Ming dynasty event]
-
A.
Ming dynasty era
The Ming dynasty era was a period in Chinese history (1368–1644) marked by native Han rule, strong centralized bureaucracy, flourishing arts and literature, extensive maritime trade, and major architectural achievements such as the Forbidden City and sections of the Great Wall.
-
B.
Ming dynasty person
A Ming dynasty person is an individual who lived under the rule of China’s Ming dynasty (1368–1644), participating in its social, political, economic, or cultural life.
-
C.
Yuan dynasty era
The Yuan dynasty era refers to the period (1271–1368) when the Mongol-led Yuan dynasty ruled China, marked by vast Eurasian integration, cultural exchange, and significant developments in administration, trade, and the arts.
-
D.
Ming dynasty architecture
Ming dynasty architecture is a style of Chinese building characterized by strict symmetry, axial layouts, timber-frame construction with bracket sets (dougong), raised platforms, and elaborately decorated roofs with glazed tiles, reflecting imperial authority and Confucian order.
-
E.
Ming dynasty emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:32 a.m.