Triple
T5985471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangxu Emperor |
E133214
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object |
Dezong
Dezong is the posthumous temple name of the Guangxu Emperor, a late Qing dynasty ruler of China.
|
E560005
|
NE FINISHED |
How this triple was built (4 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Dezong | Statement: [Guangxu Emperor, templeName, Dezong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dezong Context triple: [Guangxu Emperor, templeName, Dezong]
-
A.
Dezhi
Dezhi is the courtesy name of the Xuande Emperor, a Ming dynasty ruler of China known for his relatively stable and prosperous reign in the early 15th century.
-
B.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
C.
Muzong
Muzong is the temple name of the Longqing Emperor, a Ming dynasty ruler of China who reigned from 1567 to 1572.
-
D.
Deyu
Deyu is the courtesy name of the Hongguang Emperor, a short-lived Southern Ming ruler who attempted to restore the Ming dynasty after the fall of Beijing to the Qing.
-
E.
Zhenjin
Zhenjin was the designated heir and favored son of Kublai Khan, known for his Confucian education and role in the early Yuan dynasty’s administration before his premature death.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Dezong Triple: [Guangxu Emperor, templeName, Dezong]
Generated description
Dezong is the posthumous temple name of the Guangxu Emperor, a late Qing dynasty ruler of China.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Dezong Target entity description: Dezong is the posthumous temple name of the Guangxu Emperor, a late Qing dynasty ruler of China.
-
A.
Dezhi
Dezhi is the courtesy name of the Xuande Emperor, a Ming dynasty ruler of China known for his relatively stable and prosperous reign in the early 15th century.
-
B.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
C.
Muzong
Muzong is the temple name of the Longqing Emperor, a Ming dynasty ruler of China who reigned from 1567 to 1572.
-
D.
Deyu
Deyu is the courtesy name of the Hongguang Emperor, a short-lived Southern Ming ruler who attempted to restore the Ming dynasty after the fall of Beijing to the Qing.
-
E.
Zhenjin
Zhenjin was the designated heir and favored son of Kublai Khan, known for his Confucian education and role in the early Yuan dynasty’s administration before his premature death.
- F. None of above. chosen
Provenance (5 batches)
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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6dcaf08190bac27c7042e65e07 |
completed | March 22, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e42a0fcc8190ab8d7f797b58a8e0 |
completed | March 23, 2026, 6:56 a.m. |
| NEDg | Description generation | batch_69c0f6e214748190a8e9452353853da4 |
completed | March 23, 2026, 8:16 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c0f74c175c81909d4414ca34fa85dd |
completed | March 23, 2026, 8:18 a.m. |
Created at: March 22, 2026, 4:04 p.m.