Triple
T7946636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuanxu |
E184514
|
entity |
| Predicate | nameInChinese |
P4878
|
FINISHED |
| Object | 顓頊 |
E184514
|
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: 顓頊 | Statement: [Zhuanxu, nameInChinese, 顓頊]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 顓頊 Context triple: [Zhuanxu, nameInChinese, 顓頊]
-
A.
Zhuanxu
chosen
Zhuanxu is a legendary ancient Chinese emperor and cultural hero, traditionally regarded as one of the Five Emperors and an important ancestral figure in early Chinese myth and royal genealogies.
-
B.
Huangdi
Huangdi is the Chinese term for "emperor," denoting the supreme sovereign of imperial China.
-
C.
Xiaojing Huangdi
Xiaojing Huangdi is the posthumous temple name of Emperor Jing of Han, a Western Han dynasty ruler known for consolidating imperial power and promoting economic stability in ancient China.
-
D.
Li Shang
Li Shang is a disciplined and honorable Chinese army captain who becomes Mulan’s commanding officer and eventual love interest in Disney’s animated film "Mulan."
-
E.
Dongyue Emperor
The Dongyue Emperor is a major Taoist deity revered as the sovereign of Mount Tai and a powerful judge of the underworld and human fate.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b29a570819091a2ac185a8d57c4 |
completed | March 31, 2026, 3:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe02faa308190aeba83cc6cb96153 |
completed | March 31, 2026, 2:54 p.m. |
Created at: March 30, 2026, 5:09 p.m.