Triple
T18378688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōhime |
E446383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | daughter of a shogun |
C40432
|
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: daughter of a shogun Context triple: [Ōhime, instanceOf, daughter of a shogun]
-
A.
commoner-born empress consort of Japan
A commoner-born empress consort of Japan is a woman of non-aristocratic, non-imperial origin who marries the reigning emperor and assumes the formal role and duties of empress consort within the Japanese imperial household.
-
B.
daimyo wife
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.
-
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.
princess of Japan
A princess of Japan is a female member of the Japanese imperial family, typically the daughter or close female relative of the reigning emperor or crown prince, who holds a ceremonial and symbolic role within the nation's constitutional monarchy.
-
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. 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:45 a.m.