Triple
T36155264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yūgao |
E1045712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Genji’s lover |
C44079
|
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: Genji’s lover Context triple: [Yūgao, instanceOf, Genji’s lover]
-
A.
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.
-
B.
ancient Japanese noblewoman
An ancient Japanese noblewoman is an aristocratic lady of the imperial court, distinguished by her refined education, elaborate dress such as layered kimono, and participation in the political, literary, and ceremonial life of classical Japan.
-
C.
Ō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.
-
D.
fictional Japanese noblewoman
chosen
A fictional Japanese noblewoman is an imagined high-ranking woman from Japan’s aristocracy, often depicted with refined manners, elaborate traditional dress, and a life shaped by courtly rituals, political intrigue, and cultural expectations.
-
E.
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.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.