Triple
T15020183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianqi Emperor |
E378062
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Xizong |
E378062
|
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: Xizong | Statement: [Tianqi Emperor, templeName, Xizong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xizong Context triple: [Tianqi Emperor, templeName, Xizong]
-
A.
Xizong
chosen
Xizong was the temple name of the Tianqi Emperor, a late Ming dynasty ruler known for his short, troubled reign heavily influenced by eunuch officials.
-
B.
Chengzong
Chengzong, better known as Temür Khan, was a Yuan dynasty emperor of the Mongol Empire who ruled China in the late 13th and early 14th centuries.
-
C.
Yuanzong
Yuanzong is the courtesy name of Sun Hao, the last emperor of Eastern Wu during China’s Three Kingdoms period.
-
D.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
E.
Huiguo
Huiguo was a prominent Chinese Buddhist monk of the Tang dynasty and a key master of Esoteric Buddhism who played a crucial role in transmitting these teachings to the Japanese monk Kūkai (Kobo Daishi).
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded76445988190984b57de66e00c4a |
completed | April 15, 2026, 12:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9dd078e481908ec78db57541fc4c |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:56 a.m.