Triple
T5724164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashikuni |
E126220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese princely house |
C16771
|
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: Japanese princely house Context triple: [Higashikuni, instanceOf, Japanese princely house]
-
A.
branch of the Japanese Imperial Family
chosen
A branch of the Japanese Imperial Family is a collateral line descended from the main imperial lineage, historically established to support succession, fulfill ceremonial duties, and maintain the continuity and stability of the imperial institution.
-
B.
member of the Japanese imperial family
A member of the Japanese imperial family is an individual related by blood or adoption to the Emperor of Japan, holding a formal status defined by the Imperial Household Law and participating in ceremonial, cultural, and representational duties of the monarchy.
-
C.
head of the Tokugawa family
The head of the Tokugawa family is the hereditary leader of the Tokugawa clan, historically serving as the shogun or principal patriarch guiding the family's political, social, and cultural legacy in Japan.
-
D.
Japanese monarch
A Japanese monarch is the hereditary sovereign of Japan, traditionally regarded as a symbolic and unifying figurehead of the nation and its people.
-
E.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:47 p.m.