Triple
T3874023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Nekka |
E92453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kwantung Army operation |
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: Kwantung Army operation Context triple: [Operation Nekka, instanceOf, Kwantung Army operation]
-
A.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
B.
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.
-
C.
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.
-
D.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
E.
anti-Chinese incident
An anti-Chinese incident is an event or action, ranging from verbal harassment to physical violence or discriminatory policies, specifically targeting individuals, communities, or institutions perceived as Chinese.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.