Triple
T27150080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatsuhime |
E682362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | daimyō wife |
C21714
|
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: daimyō wife Context triple: [Hatsuhime, instanceOf, daimyō wife]
-
A.
daimyo wife
chosen
A daimyo wife is the spouse of a powerful feudal lord in Japan, often responsible for managing the household, forging political alliances through marriage ties, and upholding the prestige and continuity of the clan.
-
B.
Ō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.
-
C.
daughter of a shogun
A daughter of a shogun is a high-born woman of feudal Japan whose life is shaped by political alliances, strict social expectations, and the prestige and dangers of her father’s military rule.
-
D.
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.
-
E.
concubine of the Japanese emperor
A concubine of the Japanese emperor was a woman of lower rank than the empress or official consorts who lived within the imperial court to bear children and support the emperor, often playing roles in court politics, culture, and succession.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:13 a.m.