Triple
T23397565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikasa |
E559403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese imperial 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 imperial family name Context triple: [Mikasa, instanceOf, Japanese imperial family name]
-
A.
Japanese honorific name
A Japanese honorific name is a personal name accompanied by a respectful suffix (such as -san, -sama, -kun, or -chan) that reflects the social relationship, status, and level of politeness between speaker and referent.
-
B.
Japanese aristocratic family
A Japanese aristocratic family is a high-ranking lineage traditionally associated with noble titles, courtly status, and inherited social prestige within Japan’s historical class system.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:37 p.m.