Triple
T36820862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine Gonzaga |
E909878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of House of Gonzaga |
C65914
|
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 House of Gonzaga Context triple: [Catherine Gonzaga, instanceOf, member of House of Gonzaga]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.