Triple
T16467619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianshun Emperor |
E399975
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Jingtai |
E74288
|
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: Jingtai | Statement: [Tianshun Emperor, eraName, Jingtai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jingtai Context triple: [Tianshun Emperor, eraName, Jingtai]
-
A.
Xuande
Xuande is the courtesy name of Liu Bei, the founding emperor of the Shu Han state during China’s Three Kingdoms period.
-
B.
Yongyuan
Yongyuan was the era name used during part of Emperor Zhang's rule in the Eastern Han dynasty of ancient China.
-
C.
Xuande era
The Xuande era was a period of the early Ming dynasty in China marked by relative political stability, competent governance, and flourishing arts under the rule of the Xuande Emperor.
-
D.
Zhanxi
Zhanxi is a Chinese given name, here referring to the personal name of an individual surnamed Zhu.
-
E.
Jingtai Emperor
chosen
The Jingtai Emperor was a 15th-century ruler of China's Ming dynasty whose short and turbulent reign followed the capture of his brother, the Zhengtong Emperor, by Mongol forces.
- 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.