Triple

T18522431
Position Surface form Disambiguated ID Type / Status
Subject Grigory Shtern E452620 entity
Predicate conflict P12 FINISHED
Object Sino-Soviet conflict of 1929 NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Sino-Soviet conflict of 1929 | Statement: [Grigory Shtern, conflict, Sino-Soviet conflict of 1929]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sino-Soviet conflict of 1929
Context triple: [Grigory Shtern, conflict, Sino-Soviet conflict of 1929]
  • A. Sino–Soviet split
    The Sino–Soviet split was the major ideological and political rift between the Soviet Union and the People’s Republic of China during the Cold War, which reshaped global communist alliances and international relations in the 1960s and 1970s.
  • B. Sino–Soviet border conflict
    The Sino–Soviet border conflict was a series of armed clashes in 1969 between the Soviet Union and the People’s Republic of China along their disputed frontier, marking the peak of tensions in the Sino–Soviet split.
  • C. Nomonhan Incident
    The Nomonhan Incident was a 1939 border war between Japan and the Soviet Union (with Mongolia) near the Khalkhin Gol river that ended in a decisive Soviet victory and helped deter further Japanese expansion into Siberia.
  • D. Mukden Incident
    The Mukden Incident was a staged 1931 explosion on a Japanese-controlled railway in Manchuria used by Japan as a pretext to invade and occupy the region.
  • E. Marco Polo Bridge Incident
    The Marco Polo Bridge Incident was a 1937 armed clash between Japanese and Chinese troops near Beijing that escalated into full-scale war between Japan and China.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Sino-Soviet conflict of 1929
Target entity description: The Sino-Soviet conflict of 1929 was a brief armed clash between the Soviet Union and the Republic of China over control of the Chinese Eastern Railway in Manchuria.
  • A. Sino–Soviet split
    The Sino–Soviet split was the major ideological and political rift between the Soviet Union and the People’s Republic of China during the Cold War, which reshaped global communist alliances and international relations in the 1960s and 1970s.
  • B. Sino–Soviet border conflict
    The Sino–Soviet border conflict was a series of armed clashes in 1969 between the Soviet Union and the People’s Republic of China along their disputed frontier, marking the peak of tensions in the Sino–Soviet split.
  • C. Nomonhan Incident
    The Nomonhan Incident was a 1939 border war between Japan and the Soviet Union (with Mongolia) near the Khalkhin Gol river that ended in a decisive Soviet victory and helped deter further Japanese expansion into Siberia.
  • D. Mukden Incident
    The Mukden Incident was a staged 1931 explosion on a Japanese-controlled railway in Manchuria used by Japan as a pretext to invade and occupy the region.
  • E. Marco Polo Bridge Incident
    The Marco Polo Bridge Incident was a 1937 armed clash between Japanese and Chinese troops near Beijing that escalated into full-scale war between Japan and China.
  • F. None of above. chosen

Provenance (2 batches)

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_69d8d386df84819092355ebb260d848e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5338f6da48190bdb374019d10db05 completed April 19, 2026, 7:57 p.m.
Created at: April 10, 2026, 11:37 a.m.