Triple
T27481147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gengshi Emperor |
E693605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Han dynasty emperor |
C13056
|
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: Han dynasty emperor Context triple: [Gengshi Emperor, instanceOf, Han dynasty emperor]
-
A.
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.
-
B.
emperor of China
chosen
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.
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.
-
D.
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.
-
E.
Ming dynasty emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 12:59 p.m.