Triple
T23408707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangxu Emperor |
E560005
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Dezong |
—
|
NE NERFINISHED |
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: [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.
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.
Yizong
Yizong was the temple name of an emperor of the Tang dynasty who ruled China during the mid-9th century.
-
D.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
E.
Aizong
Aizong is the temple name of Emperor Ai of the Tang dynasty, a short-reigning and final ruler associated with the dynasty’s decline.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
Created at: April 17, 2026, 5:38 p.m.