Triple
T7946632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuanxu |
E184514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary Chinese emperor |
C12083
|
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: legendary Chinese emperor Context triple: [Zhuanxu, instanceOf, legendary Chinese emperor]
-
A.
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.
-
B.
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.
-
C.
Chinese monarch
chosen
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.
-
D.
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.
-
E.
ancient Chinese person
An ancient Chinese person is an individual who lived in historical China, shaped by its dynastic rule, philosophical traditions like Confucianism and Daoism, and distinctive cultural practices, technologies, and social structures of the time.
- 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.