Triple
T16642835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaojing |
E404385
|
entity |
| Predicate | spouseOf |
P13
|
FINISHED |
| Object | Zhu Zaiji |
E426271
|
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: Zhu Zaiji | Statement: [Empress Xiaojing, spouseOf, Zhu Zaiji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhu Zaiji Context triple: [Empress Xiaojing, spouseOf, Zhu Zaiji]
-
A.
Zhu Zaiji
chosen
Zhu Zaiji, better known as the Longqing Emperor, was a Ming dynasty ruler who briefly stabilized the empire and reopened trade after the tumultuous reign of his father, the Jiajing Emperor.
-
B.
Zhu Cijiong
Zhu Cijiong was a Qing dynasty imperial prince, known as one of the sons of the Chongzhen Emperor, the last ruler of the Ming dynasty.
-
C.
Zhu Cijiong
Zhu Cijiong was a Ming dynasty imperial prince, known primarily as a younger brother of the ill-fated Princess Changping during the dynasty’s final years.
-
D.
Zhu Houxi
Zhu Houxi was a Ming dynasty imperial prince, known primarily as a son of the Hongzhi Emperor of China.
-
E.
Zhu Zhanxi
Zhu Zhanxi was a Ming dynasty imperial prince, notable as a son of the short-reigning Hongxi Emperor of China.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad27b5481908316b4f23fb8bc32 |
completed | April 18, 2026, 12:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014136275c819084da2756632e0f48 |
completed | May 11, 2026, 2:38 a.m. |
Created at: April 10, 2026, 5:18 a.m.