Triple
T31086405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Min of Jin |
E792252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Jin emperor |
C58610
|
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: Western Jin emperor Context triple: [Emperor Min of Jin, instanceOf, Western Jin emperor]
-
A.
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.
-
B.
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.
-
C.
Eastern Wu emperor
An Eastern Wu emperor is the sovereign ruler of the Eastern Wu state during China’s Three Kingdoms period, holding supreme political, military, and ceremonial authority over its territories and subjects.
-
D.
emperor of Cao Wei
The emperor of Cao Wei was the sovereign ruler of the Cao Wei state during China’s Three Kingdoms period, holding supreme political, military, and ceremonial authority over its territories and subjects.
-
E.
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.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.