Triple
T8186139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ling of Han |
E191188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Han dynasty 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: Eastern Han dynasty emperor Context triple: [Emperor Ling of Han, instanceOf, Eastern Han dynasty 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.
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.
-
C.
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.
-
D.
Chinese monarch
A Chinese monarch is the supreme hereditary ruler of a Chinese state or dynasty, holding ultimate political, military, and ritual authority within a traditionally centralized imperial system.
-
E.
Korean emperor
A Korean emperor is the supreme hereditary monarch who holds the highest sovereign authority over a unified Korean state, historically or in a conceptual context.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:41 p.m.