Triple
T36993896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihon Kōki |
E915178
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese historical chronicle |
C29465
|
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 historical chronicle Context triple: [Nihon Kōki, instanceOf, Japanese historical chronicle]
-
A.
Japanese historical tale
A Japanese historical tale is a narrative work that recounts and embellishes real past events, figures, and battles in Japan’s history, blending factual record with literary storytelling.
-
B.
Rikkokushi
chosen
Rikkokushi is the collective term for the six earliest official Japanese national histories, compiled in classical Chinese between the 8th and 9th centuries, documenting Japan’s mythic origins through the early Heian period.
-
C.
Edo-period literary work
An Edo-period literary work is a piece of Japanese literature produced between 1603 and 1868 that reflects the era’s urban culture, social changes, and evolving literary forms such as ukiyo-zōshi, haikai, and kabuki-related texts.
-
D.
Japanese classic text
A Japanese classic text is a historically significant written work from Japan’s premodern eras that reflects traditional language, culture, thought, and literary or scholarly practices.
-
E.
Japanese historical event
A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.