Triple
T3647835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taichang Emperor |
E77344
|
entity |
| Predicate | reignName |
P32785
|
FINISHED |
| Object | Taichang |
E376388
|
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: Taichang | Statement: [Taichang Emperor, reignName, Taichang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taichang Context triple: [Taichang Emperor, reignName, Taichang]
-
A.
Taichang
chosen
Taichang was the posthumous temple name of a short-reigning Ming dynasty emperor who ruled China briefly in 1620.
-
B.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
C.
Tudigong
Tudigong is a widely venerated Chinese earth god and local tutelary deity associated with protecting land, villages, and community welfare.
-
D.
Yongli
Yongli was the era name of the last emperor of the Southern Ming dynasty, whose reign marked the final resistance of Ming loyalists against the Qing conquest in 17th-century China.
-
E.
Zhizhong
Zhizhong is a Chinese given name shared by various individuals, including historical and contemporary figures.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38aa2388190bf1af926375e2433 |
completed | March 8, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b48836f5d08190bbf0b6410ed6f766 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:24 p.m.