Triple
T26394486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | legend of the three arrows |
E663509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese historical legend |
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: Japanese historical legend Context triple: [legend of the three arrows, instanceOf, Japanese historical legend]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Shinto mythological event
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.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:28 p.m.