Triple
T17087992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanli Emperor |
E414650
|
entity |
| Predicate | personalName |
P24312
|
FINISHED |
| Object | Zhu Yijun |
—
|
NE NERFINISHED |
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 Yijun | Statement: [Wanli Emperor, personalName, Zhu Yijun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhu Yijun Context triple: [Wanli Emperor, personalName, Zhu Yijun]
-
A.
Zhu Yijun
chosen
Zhu Yijun was the Ming dynasty ruler better known as the Wanli Emperor, whose long reign from 1572 to 1620 saw both early prosperity and later decline of the dynasty.
-
B.
Zhu Junyi
Zhu Junyi is a former senior Chinese police and security official best known for his involvement in major corruption scandals.
-
C.
Zhu Yunjian
Zhu Yunjian was a Ming dynasty imperial prince, known as a descendant of the Hongwu Emperor through his son Zhu Biao.
-
D.
Zhu Jun
Zhu Jun was a prominent late Eastern Han dynasty general and official known for his role in suppressing major uprisings and helping to stabilize imperial authority.
-
E.
Zhu Zhanyong
Zhu Zhanyong was a Ming dynasty imperial prince, known primarily as a son of the Hongxi Emperor of China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
Created at: April 10, 2026, 5:35 a.m.