Triple
T9348726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Dezong of Tang |
E224960
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Dezong |
E560005
|
NE FINISHED |
How this triple was built (2 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: [Emperor Dezong of Tang, templeName, Dezong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dezong Context triple: [Emperor Dezong of Tang, templeName, Dezong]
-
A.
Dezong
chosen
Dezong is the posthumous temple name of the Guangxu Emperor, a late Qing dynasty ruler of China.
-
B.
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.
-
C.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
D.
Muzong
Muzong is the temple name of the Longqing Emperor, a Ming dynasty ruler of China who reigned from 1567 to 1572.
-
E.
Chongde
Chongde was the era name used by Qing dynasty ruler Hong Taiji for the final years of his reign in the early 17th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f107f0081908938f4b814eca5fc |
completed | April 1, 2026, 5 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e432106c81908ae080f37bc80f3f |
completed | April 4, 2026, 10:13 a.m. |
Created at: March 30, 2026, 7:41 p.m.