Triple
T4822083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Mikasa |
E107733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Imperial House of Japan |
C3248
|
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 the Imperial House of Japan Context triple: [Prince Mikasa, instanceOf, member of the Imperial House of Japan]
-
A.
member of the Japanese imperial family
chosen
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.
-
B.
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.
-
C.
peer of the Empire of Japan
A peer of the Empire of Japan was a member of the kazoku hereditary nobility, holding aristocratic rank and privileges under the Meiji Constitution and subsequent imperial government.
-
D.
prince of the Empire of Japan
A prince of the Empire of Japan was a male member of the imperial family, typically born into or granted princely rank, who held hereditary status, court titles, and ceremonial or political roles within the pre-1947 Japanese imperial system.
-
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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.