Triple
T16899014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tale of the Heike |
E424385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Japanese literature |
C14860
|
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: medieval Japanese literature Context triple: [The Tale of the Heike, instanceOf, medieval Japanese literature]
-
A.
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.
-
B.
Japanese historical tale
chosen
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
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.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
E.
Kamakura-period document
A Kamakura-period document is a written record produced in Japan between 1185 and 1333, typically reflecting the political, legal, religious, or social practices of the emerging samurai government and contemporary society.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.