Triple
T19417175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuni no miya Kunihito |
E485751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of a collateral imperial branch |
C20916
|
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 a collateral imperial branch Context triple: [Kuni no miya Kunihito, instanceOf, member of a collateral imperial branch]
-
A.
founder of an imperial collateral branch
The founder of an imperial collateral branch is the royal family member who establishes a new, secondary line of descent related to but distinct from the main imperial lineage.
-
B.
member of extended royal family
chosen
A member of the extended royal family is an individual related by blood, marriage, or adoption to the reigning monarch or core royal line, but who holds a more distant position in the line of succession and typically fewer official duties.
-
C.
dynastic branch
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
-
D.
illegitimate royal descendant
An illegitimate royal descendant is a person born outside of lawful marriage to a member of a royal family, who may possess royal blood but typically lacks formal dynastic rights or recognition.
-
E.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:37 p.m.