Triple
T23172504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Hare of Inaba |
E578895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese mythological tale |
C46028
|
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 mythological tale Context triple: [White Hare of Inaba, instanceOf, Japanese mythological tale]
-
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.
Shinto mythological event
chosen
A Shinto mythological event is a significant occurrence or episode in Japanese Shinto tradition involving kami (deities or spirits), sacred places, and ritual actions that explain the origins, order, or spiritual nature of the world.
-
C.
Japanese folk hero
A Japanese folk hero is a legendary or semi-legendary figure from Japanese tradition whose extraordinary deeds, virtues, or cleverness embody cultural values and inspire popular stories, songs, and festivals.
-
D.
Chinese legend
A Chinese legend is a traditional narrative from Chinese culture that blends historical events, folklore, mythology, and moral lessons, passed down through generations to explain the world and convey cultural values.
-
E.
Korean foundation myth
A Korean foundation myth is a traditional narrative that explains the divine or heroic origins of the Korean people, their first rulers, and the establishment of early Korean states.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:04 p.m.