Triple
T38654423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Kōtoku |
E939850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century Japanese monarch |
C15982
|
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: 7th-century Japanese monarch Context triple: [Emperor Kōtoku, instanceOf, 7th-century Japanese monarch]
-
A.
Nara-period noble
A Nara-period noble is an aristocrat of 8th-century Japan who held political, courtly, and cultural authority within the imperial capital at Heijō-kyō, shaped by Chinese-inspired legal codes and Buddhist patronage.
-
B.
legendary Japanese empress consort
A legendary Japanese empress consort is a mythic or semi-historical imperial wife in Japan’s early chronicles, often credited with extraordinary virtues, political influence, or supernatural associations that shaped foundational narratives of the imperial line.
-
C.
Japanese monarch
chosen
A Japanese monarch is the hereditary sovereign of Japan, traditionally regarded as a symbolic and unifying figurehead of the nation and its people.
-
D.
Yamashina-no-miya prince
A Yamashina-no-miya prince is a male member of the Yamashina branch of Japan’s imperial family, historically established as one of the shinnōke or ōke houses eligible to provide a successor to the Chrysanthemum Throne.
-
E.
ancient Japanese noblewoman
An ancient Japanese noblewoman is an aristocratic lady of the imperial court, distinguished by her refined education, elaborate dress such as layered kimono, and participation in the political, literary, and ceremonial life of classical Japan.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.