Triple
T28754955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Wuyu of Yue |
E731644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Yue |
C54913
|
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: ruler of Yue Context triple: [King Wuyu of Yue, instanceOf, ruler of Yue]
-
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.
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.
-
C.
Jin state ruler
A Jin state ruler is the sovereign leader of the ancient Chinese state of Jin, responsible for governing its territories, commanding its military, and managing its political and diplomatic affairs during the Zhou dynasty period.
-
D.
King of Anshan
The "King of Anshan" is a conceptual class representing the sovereign ruler of the ancient Elamite city-state of Anshan, embodying political authority, territorial control, and dynastic legitimacy within that historical context.
-
E.
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.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:09 a.m.