Triple
T38292203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Yuyue |
E1022390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Zhu |
C36363
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the House of Zhu Context triple: [Zhu Yuyue, instanceOf, member of the House of Zhu]
-
A.
member of the Zhu clan
chosen
A member of the Zhu clan is an individual belonging to a historically significant Chinese lineage, often associated with shared ancestry, cultural traditions, and familial identity under the Zhu surname.
-
B.
member of the Chiang family
A member of the Chiang family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the Chiang surname and its shared heritage, responsibilities, and relationships.
-
C.
Eastern Wu royal family member
An Eastern Wu royal family member is an individual belonging by blood or marriage to the ruling house of the Eastern Wu state during China’s Three Kingdoms period, holding hereditary status, political influence, and potential succession rights.
-
D.
Qing dynasty prince
A Qing dynasty prince is a male member of the imperial Aisin Gioro clan who holds a hereditary noble title within the hierarchical peerage system of the Qing Empire, often bearing political, military, or ceremonial responsibilities.
-
E.
member of the Jochid dynasty
A member of the Jochid dynasty is an individual descended from Jochi, the eldest son of Genghis Khan, belonging to the ruling lineage that governed the Golden Horde and related successor states.
- F. None of above.
Provenance (1 batch)
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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.