Triple
T7062262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takamado |
E164246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese imperial house branch |
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 imperial house branch Context triple: [Takamado, instanceOf, Japanese imperial house branch]
-
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.
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.
-
C.
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.
-
D.
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.
-
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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:38 p.m.