Triple
T17071747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongcheng |
E414237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qianlong Emperor’s son |
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: Qianlong Emperor’s son Context triple: [Yongcheng, instanceOf, Qianlong Emperor’s son]
-
A.
consort of the Qianlong Emperor
A consort of the Qianlong Emperor is a woman who held an official rank within the imperial harem of the Qing dynasty, serving as one of the emperor’s recognized wives or concubines with defined status, duties, and privileges at the Qing court.
-
B.
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.
-
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.
Manchukuo emperor
A Manchukuo emperor is the sovereign ruler and symbolic head of state of the Japanese-established puppet kingdom of Manchukuo (1932–1945), most notably embodied by Puyi, the last Qing emperor.
-
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.