Triple
T31422287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Ying |
E801563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tang dynasty crown 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 crown prince Context triple: [Li Ying, instanceOf, Tang dynasty crown 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.
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.
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.
-
D.
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.
-
E.
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.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:49 p.m.