Triple
T28823742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Yamashina Kikumaro |
E727842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yamashina-no-miya prince |
C55269
|
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: Yamashina-no-miya prince Context triple: [Prince Yamashina Kikumaro, instanceOf, Yamashina-no-miya prince]
-
A.
Jochid prince
A Jochid prince is a male royal descendant of Jochi, the eldest son of Genghis Khan, belonging to the Jochid lineage that ruled and influenced territories of the Golden Horde and related Mongol successor states.
-
B.
Ōshū Fujiwara
Ōshū Fujiwara was a powerful noble clan that ruled the Hiraizumi region of northern Japan in the late Heian period, flourishing through control of gold resources and trade before being destroyed by Minamoto no Yoritomo in 1189.
-
C.
King of Ryukyu
The King of Ryukyu was the sovereign ruler of the Ryukyu Kingdom, overseeing its political authority, tributary diplomacy (especially with China and Japan), and the governance of its island domains.
-
D.
Shunga ruler
A Shunga ruler is a monarch from the Shunga dynasty (c. 185–73 BCE) in ancient India, known for governing a post-Mauryan empire centered in northern and central India and for patronizing Brahmanical traditions and early art.
-
E.
Ryukyuan lord
A Ryukyuan lord was a regional noble of the Ryukyu Kingdom who governed local territories, managed tribute and trade, and served the royal court in a hierarchical feudal system influenced by both Japanese and Chinese cultures.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:35 a.m.