Triple
T35101997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa Tsunayoshi |
E1013044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tokugawa shogun |
C15548
|
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: Tokugawa shogun Context triple: [Tokugawa Tsunayoshi, instanceOf, Tokugawa shogun]
-
A.
head of the Tokugawa family
chosen
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.
-
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.
Yamashina-no-miya prince
A Yamashina-no-miya prince is a male member of the Yamashina branch of Japan’s imperial family, historically established as one of the shinnōke or ōke houses eligible to provide a successor to the Chrysanthemum Throne.
-
D.
Meiji oligarch
A Meiji oligarch was a member of the small, elite group of Japanese leaders who, after the 1868 Meiji Restoration, directed the country’s rapid modernization and centralization of political power.
-
E.
Ō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.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.