Triple
T33329565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakatsuhime no Ōkimi |
E853364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Yamato court |
C61614
|
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 Yamato court Context triple: [Nakatsuhime no Ōkimi, instanceOf, member of the Yamato court]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
member of the Higashikuni-no-miya house
A member of the Higashikuni-no-miya house is an individual belonging to a former collateral branch of the Japanese Imperial Family, historically holding princely status and close ties to the main imperial line.
-
E.
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.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.