Triple
T16731372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonglian |
E406599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty imperial prince |
C28895
|
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: Qing dynasty imperial prince Context triple: [Yonglian, instanceOf, Qing dynasty imperial prince]
-
A.
Qing dynasty prince
chosen
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.
Qing dynasty viceroy
A Qing dynasty viceroy was a high-ranking imperial official who governed one or more provinces, overseeing civil administration, military affairs, and tax collection on behalf of the emperor.
-
C.
Ming dynasty emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
-
D.
regent of China
A regent of China is an individual appointed to govern the Chinese state on behalf of an emperor who is unable to rule directly, typically due to minority, incapacity, or absence.
-
E.
crown prince of the Mughal Empire
The crown prince of the Mughal Empire was the designated heir apparent, usually the emperor’s eldest surviving son, who held significant political influence and military command while awaiting succession to the throne.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.