Triple
T31496916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Yun |
E803569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tang dynasty imperial prince |
C56188
|
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: Tang dynasty imperial prince Context triple: [Li Yun, instanceOf, Tang dynasty imperial prince]
-
A.
Tang dynasty prince
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Tang dynasty official
A Tang dynasty official is a government administrator or bureaucrat serving the Tang Empire, typically selected through the imperial examination system to manage civil, military, and fiscal affairs.
-
E.
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.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:41 p.m.