Triple
T23763696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengjing zhidao chuncheng zhengde hongren qinmin xianhuangdi |
E587318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese imperial posthumous name |
C33061
|
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: Chinese imperial posthumous name Context triple: [Chengjing zhidao chuncheng zhengde hongren qinmin xianhuangdi, instanceOf, Chinese imperial posthumous name]
-
A.
posthumous temple name
A posthumous temple name is an honorific title granted to a deceased ruler or notable figure, typically used in ancestral rites and historical records to encapsulate their character or reign.
-
B.
Chinese reign era name
A Chinese reign era name is an official title adopted by an emperor to designate and chronologically label a specific period of their rule, used in dating years and historical events.
-
C.
Chinese honorific name
A Chinese honorific name is a formal or respectful appellation, often incorporating titles, virtues, or status markers, used to address or refer to someone with deference in Chinese language and culture.
-
D.
temple name
chosen
A temple name is an honorific posthumous title traditionally bestowed upon East Asian monarchs or high-ranking figures, used in ancestral rites and historical records to encapsulate their reign or character.
-
E.
posthumous era name
A posthumous era name is an honorary title assigned after a ruler’s death to encapsulate and commemorate the character and achievements of their reign.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:14 p.m.