Triple
T32495567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Dan |
E830512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Han dynasty imperial prince |
C53171
|
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: Han dynasty imperial prince Context triple: [Liu Dan, instanceOf, Han dynasty imperial prince]
-
A.
Han dynasty crown prince
chosen
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.
-
B.
Tang dynasty prince
A Tang dynasty prince is a male member of the imperial family of China’s Tang dynasty, typically holding noble titles, political influence, and responsibilities in governance, military affairs, or regional administration.
-
C.
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.
-
D.
Zhou dynasty prince
A Zhou dynasty prince is a male royal family member of the Zhou dynasty, typically a son or close male relative of the king, who holds hereditary noble rank, governs fiefdoms, and participates in ritual, military, and administrative duties within the feudal order.
-
E.
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.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.