Triple
T16467618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianshun Emperor |
E399975
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Daizong |
E365517
|
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: Daizong | Statement: [Tianshun Emperor, templeName, Daizong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daizong Context triple: [Tianshun Emperor, templeName, Daizong]
-
A.
Daizong
chosen
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
B.
Shaozong
Shaozong is the posthumous temple name of the Longwu Emperor, a short-lived Ming dynasty claimant who resisted the Qing conquest in southern China.
-
C.
Tudigong
Tudigong is a widely venerated Chinese earth god and local tutelary deity associated with protecting land, villages, and community welfare.
-
D.
Yizong
Yizong was the temple name of an emperor of the Tang dynasty who ruled China during the mid-9th century.
-
E.
Houzhu
Houzhu is the posthumous temple name of Liu Shan, the last emperor of the Shu Han state during China’s Three Kingdoms period.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcd707081908fb7ca91a8c09e0a |
completed | April 18, 2026, 7:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f5914dc81908c3b8cf999ee76a1 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:11 a.m.