Triple
T37975282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanboku-chō period conflicts |
E947405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Japanese history event |
C21713
|
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 history event Context triple: [Nanboku-chō period conflicts, instanceOf, medieval Japanese history event]
-
A.
Japanese historical event
chosen
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.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
C.
Heian-period conflict
A Heian-period conflict is a historically situated struggle or dispute in Japan’s Heian era (794–1185), involving political, military, or social tensions among imperial, aristocratic, and emerging warrior factions.
-
D.
battle of the Genpei War
A battle of the Genpei War is a specific military engagement between the Taira and Minamoto clans during Japan’s 1180–1185 civil conflict, characterized by its participants, location, tactics, outcome, and impact on the war’s progression.
-
E.
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.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.