Triple
T17309849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Dowager Xiaozhuang |
E420265
|
entity |
| Predicate | consortRank |
P11700
|
FINISHED |
| Object |
Consort Zhuang
Consort Zhuang was a Qing dynasty imperial consort associated with Empress Dowager Xiaozhuang’s court.
|
E1261943
|
NE FINISHED |
How this triple was built (4 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 Zhuang | Statement: [Empress Dowager Xiaozhuang, consortRank, Consort Zhuang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Consort Zhuang Context triple: [Empress Dowager Xiaozhuang, consortRank, Consort Zhuang]
-
A.
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.
-
B.
Consort Guo
Consort Guo was an imperial consort of the late Tang dynasty best known as the mother of Emperor Xizong of Tang.
-
C.
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.
-
D.
Consort Wang
Consort Wang was an imperial consort of the Tang dynasty best known as the mother of Emperor Xianzong.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Consort Zhuang Triple: [Empress Dowager Xiaozhuang, consortRank, Consort Zhuang]
Generated description
Consort Zhuang was a Qing dynasty imperial consort associated with Empress Dowager Xiaozhuang’s court.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Consort Zhuang Target entity description: Consort Zhuang was a Qing dynasty imperial consort associated with Empress Dowager Xiaozhuang’s court.
-
A.
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.
-
B.
Consort Guo
Consort Guo was an imperial consort of the late Tang dynasty best known as the mother of Emperor Xizong of Tang.
-
C.
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.
-
D.
Consort Wang
Consort Wang was an imperial consort of the Tang dynasty best known as the mother of Emperor Xianzong.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439970cf08190bc9e49ba830da0d9 |
completed | April 19, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180e30934819087b7c838c8874aff |
completed | May 11, 2026, 7:10 a.m. |
| NEDg | Description generation | batch_6a0185a7e5188190a15d835019fc226f |
completed | May 11, 2026, 7:30 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0186504460819097f80978b03c7296 |
completed | May 11, 2026, 7:33 a.m. |
Created at: April 10, 2026, 5:43 a.m.