Triple
T22054117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashikuni Toshihiko |
E544960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Higashikuni-no-miya house |
C45732
|
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: member of the Higashikuni-no-miya house Context triple: [Higashikuni Toshihiko, instanceOf, member of the Higashikuni-no-miya house]
-
A.
member of the Higashifushimi-no-miya house
A member of the Higashifushimi-no-miya house is an individual belonging to a former collateral branch of the Japanese Imperial Family historically associated with the Higashifushimi princely title.
-
B.
member of the Kuni-no-miya house
A member of the Kuni-no-miya house is an individual belonging to a former collateral branch of the Japanese Imperial Family, historically established to support and extend the imperial lineage.
-
C.
member of the Kujō family
A member of the Kujō family is an individual belonging to the historically influential Japanese aristocratic lineage associated with the Fujiwara clan and the regent houses of the Heian and Kamakura periods.
-
D.
member of the Tokugawa clan
A member of the Tokugawa clan is an individual belonging to the powerful samurai family that established and ruled Japan’s Tokugawa shogunate from 1603 to 1868, holding significant political, military, and social influence.
-
E.
member of the Shimazu clan
A member of the Shimazu clan is an individual belonging to the powerful samurai family that ruled the Satsuma domain in southern Kyushu and played a major role in Japanese political and military history.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:26 p.m.