Triple
T4069833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tairiku Datsū Sakusen |
E86617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campaign of the Second Sino-Japanese War |
C1883
|
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: campaign of the Second Sino-Japanese War Context triple: [Tairiku Datsū Sakusen, instanceOf, campaign of the Second Sino-Japanese War]
-
A.
event in the Second Sino-Japanese War
chosen
An event in the Second Sino-Japanese War is a specific historical occurrence—such as a battle, campaign, political decision, or diplomatic incident—that took place between 1937 and 1945 within the broader conflict between China and Japan.
-
B.
phase of the Chinese Civil War
A phase of the Chinese Civil War is a distinct, time-bounded period characterized by specific patterns of military conflict, political strategies, territorial control, and key events between the major opposing forces.
-
C.
phase of the Chinese Civil War
A phase of the Chinese Civil War is a distinct period characterized by specific political, military, and social dynamics that collectively define a recognizable stage in the broader conflict between the Chinese Communist Party and the Kuomintang.
-
D.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
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.
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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.