Triple
T19717207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Toshiko |
E473508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Higashikuni-no-miya family member |
C16771
|
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: Higashikuni-no-miya family member Context triple: [Princess Toshiko, instanceOf, Higashikuni-no-miya family member]
-
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 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.
-
C.
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.
-
D.
branch of the Japanese Imperial Family
chosen
A branch of the Japanese Imperial Family is a collateral line descended from the main imperial lineage, historically established to support succession, fulfill ceremonial duties, and maintain the continuity and stability of the imperial institution.
-
E.
Ashikaga clan member
An Ashikaga clan member is an individual belonging to the powerful samurai family that founded and led Japan’s Ashikaga (Muromachi) shogunate from the 14th to 16th centuries.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.