Triple
T7947535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cao Pi |
E184533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cao Wei emperor |
C13056
|
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: Cao Wei emperor Context triple: [Cao Pi, instanceOf, Cao Wei emperor]
-
A.
emperor of China
chosen
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.
-
B.
Pala emperor
A Pala emperor is a sovereign ruler of the Pala dynasty who governed large parts of the Indian subcontinent, particularly Bengal and Bihar, during the early medieval period, overseeing political administration, military campaigns, and patronage of Buddhism and culture.
-
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.
King of Anshan
The "King of Anshan" is a conceptual class representing the sovereign ruler of the ancient Elamite city-state of Anshan, embodying political authority, territorial control, and dynastic legitimacy within that historical context.
-
E.
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.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:09 p.m.