Triple
T22580825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三笠宮寛仁親王妃信子 |
E544562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 三笠宮家の一員 |
C3248
|
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: 三笠宮家の一員 Context triple: [三笠宮寛仁親王妃信子, instanceOf, 三笠宮家の一員]
-
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 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.
-
C.
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.
-
D.
member of the Japanese imperial family
chosen
A member of the Japanese imperial family is an individual related by blood or adoption to the Emperor of Japan, holding a formal status defined by the Imperial Household Law and participating in ceremonial, cultural, and representational duties of the monarchy.
-
E.
branch of the Japanese Imperial Family
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.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:53 p.m.