Triple
T16332218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jōkyū War |
E396582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict in Japan |
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: conflict in Japan Context triple: [Jōkyū War, instanceOf, conflict in Japan]
-
A.
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.
-
B.
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.
-
C.
engagement of the Russo-Japanese War
An engagement of the Russo-Japanese War is a discrete military encounter—on land, sea, or both—between Russian and Japanese forces during the 1904–1905 conflict, characterized by specific participants, location, timeframe, and tactical objectives.
-
D.
independence conflict
An independence conflict is a struggle in which a region, group, or colony seeks to break away from an existing state or authority to form its own sovereign governance.
-
E.
war in China
War in China encompasses the organized, large-scale armed conflicts that have occurred within or involving Chinese territory, states, or peoples, shaped by shifting dynasties, foreign invasions, civil strife, and modern geopolitical struggles.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.