Triple
T37491467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Fushimi Sadayuki |
E931699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Fushimi-no-miya house |
C66089
|
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 Fushimi-no-miya house Context triple: [Prince Fushimi Sadayuki, instanceOf, member of the Fushimi-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 Asaka-no-miya house
A member of the Asaka-no-miya house is an individual belonging to a former collateral branch of the Japanese Imperial Family, historically holding princely status and associated titles within the imperial nobility system.
-
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.
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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.