Triple
T11749555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōnin War |
E279370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese war |
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: Japanese war Context triple: [Ōnin War, instanceOf, Japanese war]
-
A.
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.
-
B.
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.
-
C.
batalla de la Segunda Guerra Mundial
Una batalla de la Segunda Guerra Mundial es un enfrentamiento militar específico, terrestre, naval o aéreo, ocurrido entre 1939 y 1945, que involucró fuerzas de las potencias aliadas y/o del Eje con objetivos estratégicos definidos dentro del conflicto global.
-
D.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
E.
Pacific War engagement
A Pacific War engagement is a specific military confrontation between opposing forces in the Pacific theater during World War II, encompassing actions in air, sea, and/or land domains.
- F. None of above. chosen
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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.