Triple
T10851343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Gong |
E256152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty 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 prince Context triple: [Prince Gong, instanceOf, Qing dynasty prince]
-
A.
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.
-
B.
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.
-
C.
Southern Ming emperor
A Southern Ming emperor is a ruler of the Ming loyalist regimes that continued to claim the Chinese throne in southern China after the Ming dynasty’s fall to the Qing in 1644.
-
D.
emperor of China
The emperor of China was the supreme hereditary ruler of imperial China, regarded as the Son of Heaven and the ultimate political, military, and ritual authority over the Chinese empire.
-
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. chosen
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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.