Triple
T22951137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChiYao |
E570017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary Chinese ruler |
C47055
|
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: legendary Chinese ruler Context triple: [ChiYao, instanceOf, legendary Chinese ruler]
-
A.
Zhou dynasty ruler
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.
-
B.
emperor of China
The emperor of China was the supreme hereditary ruler of imperial China, regarded as the Son of Heaven and the ultimate political, military, and ritual authority over the Chinese empire.
-
C.
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.
-
D.
regent of China
A regent of China is an individual appointed to govern the Chinese state on behalf of an emperor who is unable to rule directly, typically due to minority, incapacity, or absence.
-
E.
Jin dynasty emperor
A Jin dynasty emperor is the supreme hereditary ruler of the Jurchen-led Jin dynasty in northern China (1115–1234), holding ultimate political, military, and ritual authority over the state and its subjects.
- F. None of above. chosen
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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:46 p.m.