Triple
T28783986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Xuan of Han |
E726748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Han dynasty emperor |
C54935
|
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: Western Han dynasty emperor Context triple: [Emperor Xuan of Han, instanceOf, Western Han dynasty emperor]
-
A.
Western Han empress
A Western Han empress was the principal wife of an emperor of China’s Western Han dynasty, wielding significant political, ceremonial, and familial authority within the imperial court.
-
B.
Han dynasty crown prince
The Han dynasty crown prince was the officially designated heir to the imperial throne, typically a son of the emperor, who held a prestigious but precarious position at the center of court politics and succession struggles.
-
C.
Xin dynasty emperor
A Xin dynasty emperor is the sovereign ruler of the short-lived Xin dynasty (9–23 CE) in Chinese history, holding supreme political, military, and ritual authority over the empire.
-
D.
Jin dynasty emperor
A Jin dynasty emperor is the supreme hereditary ruler of the Jurchen-led Jin dynasty in northern China (1115–1234), holding ultimate political, military, and ritual authority over the state and its subjects.
-
E.
Han dynasty princess
A Han dynasty princess is an imperial daughter or close female relative of the Han emperor, whose status, marriages, and political roles were used to secure alliances, consolidate power, and embody the prestige of the ruling house in ancient 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:20 a.m.