Triple
T13324818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Gui |
E317412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty princely peerage |
C18227
|
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 princely peerage Context triple: [Prince of Gui, instanceOf, Ming dynasty princely peerage]
-
A.
Qing dynasty prince
A Qing dynasty prince is a male member of the imperial Aisin Gioro clan who holds a hereditary noble title within the hierarchical peerage system of the Qing Empire, often bearing political, military, or ceremonial responsibilities.
-
B.
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.
-
C.
Ming dynasty person
chosen
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.
-
D.
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.
-
E.
Southern Ming emperor
A Southern Ming emperor is a ruler of the Ming loyalist regimes that continued to claim the Chinese throne in southern China after the Ming dynasty’s fall to the Qing in 1644.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:30 p.m.