Triple
T10150176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaka |
E232613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese noble family name |
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 noble family name Context triple: [Asaka, instanceOf, Japanese noble family name]
-
A.
Japanese given name
A Japanese given name is a personal name assigned at birth or during naming ceremonies in Japan, typically written in kanji, hiragana, or katakana, and often chosen for its meaning, sound, and cultural significance.
-
B.
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.
-
C.
Latin family name
A Latin family name is a hereditary surname of Latin origin, often derived from personal names, occupations, locations, or characteristic traits, used to identify and distinguish members of a family lineage.
-
D.
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.
-
E.
namesake family
A namesake family is a family whose surname or identity is shared with, derived from, or prominently associated with a particular person, place, institution, or entity.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:08 p.m.