Triple
T20668599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikkokushi |
E507958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese national history |
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 national history Context triple: [Rikkokushi, instanceOf, Japanese national history]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Japanese war
Japanese war is a conceptual class representing organized, large-scale armed conflicts involving Japan, encompassing their political causes, military strategies, cultural impacts, and historical consequences.
-
E.
Japanese literature period
A Japanese literature period is a distinct historical era in Japan characterized by its prevailing literary forms, themes, languages, and cultural influences that shape the production and reception of written works.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:44 a.m.