Triple
T11975371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenmu Restoration |
E285026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Japanese history |
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: event in Japanese history Context triple: [Kenmu Restoration, instanceOf, event in Japanese history]
-
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.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
-
C.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
-
D.
Javanese historical event
A Javanese historical event is a significant occurrence in the past that took place in Java or involved Javanese people, shaping the island’s political, social, cultural, or religious development.
-
E.
historic event
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.