Triple
T16503962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Qiyu |
E400872
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Prince of Cheng |
E365521
|
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: Prince of Cheng | Statement: [Zhu Qiyu, title, Prince of Cheng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prince of Cheng Context triple: [Zhu Qiyu, title, Prince of Cheng]
-
A.
Prince of Cheng
chosen
The Prince of Cheng was a noble title in the Ming dynasty Chinese imperial hierarchy, held by Zhu Qiyu before he ascended the throne as the Jingtai Emperor.
-
B.
Prince of Yan
Prince of Yan was the noble title held by Zhu Di before he became the Yongle Emperor of the Ming dynasty.
-
C.
Prince of Kuaiji
The Prince of Kuaiji was the noble title held by Sun Liang, a deposed emperor of Eastern Wu during China’s Three Kingdoms period.
-
D.
Prince of Anxi
Prince of Anxi was a Yuan dynasty princely title associated with the Mongol imperial family, notably held by Manggala, a son of Kublai Khan.
-
E.
Son of Heaven
The Son of Heaven is the traditional Chinese imperial title signifying the emperor’s role as the divinely sanctioned ruler and intermediary between Heaven and the human realm.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e5100e48190a623d6ee2fefb87e |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0058305e308190a22cbd03daec53aa |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:14 a.m.