Triple
T38027889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashikaga Yoshimi |
E948829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shogunal prince |
C63587
|
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: shogunal prince Context triple: [Ashikaga Yoshimi, instanceOf, shogunal 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.
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.
-
C.
Ashikaga shogun
chosen
An Ashikaga shogun was a military ruler from the Ashikaga clan who led Japan’s Muromachi shogunate (1336–1573), exercising de facto political power while the emperor remained a largely symbolic figure.
-
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.
daimyō heir
A daimyō heir is the designated successor, usually the eldest son or an adopted relative, who is expected to inherit a feudal lord’s domain, titles, and responsibilities in premodern Japan.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.