Triple
T19618626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuni no miya Kunihide |
E470933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Kuni-no-miya house |
C42270
|
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 Kuni-no-miya house Context triple: [Kuni no miya Kunihide, instanceOf, member of the Kuni-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 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.
-
C.
member of the Minamoto clan
A member of the Minamoto clan is an individual belonging to a powerful and prestigious samurai lineage in Japan, historically influential in politics, warfare, and the establishment of the shogunate.
-
D.
Fujiwara clan member
A Fujiwara clan member is an aristocrat belonging to the powerful Fujiwara family of classical Japan, whose political influence peaked in the Heian period through strategic court positions and marital alliances with the imperial line.
-
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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.