Triple
T22580839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三笠宮寛仁親王妃信子 |
E544562
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | 三笠宮家 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 三笠宮家 | Statement: [三笠宮寛仁親王妃信子, memberOf, 三笠宮家]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 三笠宮家 Context triple: [三笠宮寛仁親王妃信子, memberOf, 三笠宮家]
-
A.
秋篠宮
秋篠宮は、日本の皇室に属する皇嗣であり、天皇徳仁の弟にあたる皇族男性である。
-
B.
三笠宮崇仁親王
chosen
三笠宮崇仁親王は、大正天皇の第四皇子であり、昭和から平成にかけて長く存命した日本の皇族で、歴史学者としても知られた人物である。
-
C.
House of Fushimi-no-miya
The House of Fushimi-no-miya was one of the four shinnōke branches of Japan’s imperial family, established to provide potential heirs to the Chrysanthemum Throne.
-
D.
Higashikuni-no-miya family
The Higashikuni-no-miya family was a collateral branch of the Japanese Imperial Family, established in the early 20th century and notable for its close ties to the main imperial line.
-
E.
Yamashina-no-miya (Imperial House of Japan)
Yamashina-no-miya was a collateral branch of the Japanese Imperial Family, established for a prince of the imperial line and historically significant within the broader structure of the Imperial House of Japan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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. |
| NER | Named-entity recognition | batch_69f15ff065308190bca9fb24b47757e6 |
completed | April 29, 2026, 1:33 a.m. |
Created at: April 16, 2026, 8:53 p.m.