Triple
T28470395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Di Xin |
E720420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shang dynasty ruler |
C23659
|
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: Shang dynasty ruler Context triple: [King Di Xin, instanceOf, Shang dynasty ruler]
-
A.
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.
-
B.
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.
-
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.
last king of the Shang dynasty
chosen
The last king of the Shang dynasty is the final monarch who ruled the Shang state before its overthrow by the Zhou, marking the end of China's second historical dynasty.
-
E.
Spring and Autumn period ruler
A Spring and Autumn period ruler is a monarch who governed one of the Chinese states between roughly 770–476 BCE, navigating complex interstate rivalries, ritual authority, and the early development of hegemonic power.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:48 a.m.