Triple
T4204847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genpei War |
E86158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war in Japan |
C441
|
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: war in Japan Context triple: [Genpei War, instanceOf, war in Japan]
-
A.
war
chosen
War is a large-scale, organized conflict between groups—typically nations or factions—characterized by sustained violence, strategic objectives, and significant political, social, and human consequences.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:49 p.m.