Triple
T30191876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhao Yuankan |
E767511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Song dynasty prince |
C55811
|
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: Song dynasty prince Context triple: [Zhao Yuankan, instanceOf, Song dynasty prince]
-
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.
Song dynasty empress
A Song dynasty empress is the principal wife of a reigning Song emperor who holds the highest female rank in the imperial court, overseeing palace affairs, ritual duties, and often influencing political and familial succession matters.
-
C.
Song dynasty noble
chosen
A Song dynasty noble is a high-ranking member of the imperial-era Chinese aristocracy who held hereditary or granted titles, land, and political influence within the sociopolitical hierarchy of the Song dynasty.
-
D.
Southern Song emperor
A Southern Song emperor was the hereditary ruler of the Southern Song dynasty (1127–1279) in China, presiding over a reduced but culturally vibrant realm centered in the south after the loss of northern territories to the Jurchen Jin and later facing the Mongol conquest.
-
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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:29 p.m.