Triple
T19448303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiroyama no tatakai |
E486543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Satsuma Rebellion |
C29745
|
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: battle of the Satsuma Rebellion Context triple: [Shiroyama no tatakai, instanceOf, battle of the Satsuma Rebellion]
-
A.
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.
-
B.
battle of the Pugachev Rebellion
A battle of the Pugachev Rebellion is an armed engagement between insurgent forces led by Yemelyan Pugachev and the troops of the Russian Empire during the 1773–1775 peasant uprising.
-
C.
Japanese invasions of Korea
The Japanese invasions of Korea (1592–1598) were a series of military campaigns launched by Toyotomi Hideyoshi’s Japan to conquer the Korean Peninsula and ultimately invade Ming China, resulting in widespread devastation, fierce resistance by Korean and Ming forces, and a prolonged regional conflict.
-
D.
Javanese military campaign
A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or strategic objectives.
-
E.
Japanese war
chosen
Japanese war is a conceptual class representing organized, large-scale armed conflicts involving Japan, encompassing their political causes, military strategies, cultural impacts, and historical consequences.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.