Triple
T23759912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Bo Qin |
E587220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Chinese noble |
C26241
|
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: ancient Chinese noble Context triple: [Duke Bo Qin, instanceOf, ancient Chinese noble]
-
A.
legendary Chinese ruler
A legendary Chinese ruler is a mythic or semi-historical sovereign from ancient Chinese tradition whose life and deeds embody foundational cultural values, political ideals, and cosmological order.
-
B.
ancient Chinese person
An ancient Chinese person is an individual who lived in historical China, shaped by its dynastic rule, philosophical traditions like Confucianism and Daoism, and distinctive cultural practices, technologies, and social structures of the time.
-
C.
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.
-
D.
Zhou dynasty ruler
chosen
A Zhou dynasty ruler is a sovereign who governed territories under the Zhou dynasty in ancient China, exercising political, military, and ritual authority within a hierarchical feudal system.
-
E.
Shang dynasty king
A Shang dynasty king was the supreme political, military, and religious ruler of the Shang state, responsible for governing territories, leading armies, and conducting divination and ritual ceremonies to communicate with ancestors and deities.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:14 p.m.