Triple
T27063617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Asaka Kikuko |
E685114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Asaka-no-miya house |
C52453
|
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 Asaka-no-miya house Context triple: [Princess Asaka Kikuko, instanceOf, member of the Asaka-no-miya house]
-
A.
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.
-
B.
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.
-
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 Takatsukasa family
A member of the Takatsukasa family is an individual belonging to the historically influential Japanese kuge (court noble) lineage that formed one of the five regent houses descended from the Fujiwara clan.
-
E.
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.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:23 a.m.