Triple

T34822057
Position Surface form Disambiguated ID Type / Status
Subject Ashikaga Yoshiteru E1003806 entity
Predicate instanceOf P0 FINISHED
Object shōgun C25451 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: shōgun
Context triple: [Ashikaga Yoshiteru, instanceOf, shōgun]
  • A. 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.
  • B. Japanese warlord chosen
    A Japanese warlord is a powerful feudal military leader who commands samurai and territories, often vying for political dominance during periods of civil strife such as the Sengoku era.
  • C. head of the Tokugawa family
    The head of the Tokugawa family is the hereditary leader of the Tokugawa clan, historically serving as the shogun or principal patriarch guiding the family's political, social, and cultural legacy in Japan.
  • 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. 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.
  • 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_69f76db717088190811b4e744610f37d completed May 3, 2026, 3:45 p.m.
Created at: May 3, 2026, 4 p.m.