Triple
T9944214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Xiu |
E194161
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object | Consort Wang |
E803566
|
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: Consort Wang | Statement: [Sun Xiu, mother, Consort Wang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Consort Wang Context triple: [Sun Xiu, mother, Consort Wang]
-
A.
Consort Wang
Consort Wang was an imperial consort of the Ming dynasty’s last ruler, the Chongzhen Emperor, known primarily for her role in the final years of the collapsing dynasty.
-
B.
Consort Wang
chosen
Consort Wang was an imperial consort of the Tang dynasty best known as the mother of Emperor Xianzong.
-
C.
Consort Guo
Consort Guo was an imperial consort of Cao Rui, the second emperor of the state of Cao Wei during China’s Three Kingdoms period.
-
D.
Consort Jia
Consort Jia was an imperial consort of the Eastern Han dynasty best known as the mother of Emperor Zhang of Han.
-
E.
Consort Yuan
Consort Yuan was an imperial consort of the late Ming dynasty and wife of the Chongzhen Emperor, associated with the dynasty’s final years before its collapse.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb613fbb48190b82a06987310cc96 |
completed | April 2, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d5095e08190a34ff73ab7bcf8a6 |
completed | April 5, 2026, 10:45 a.m. |
Created at: March 30, 2026, 8:45 p.m.