Triple

T22780428
Position Surface form Disambiguated ID Type / Status
Subject Peace Preservation Law amendments of 1928 E563820 entity
Predicate relatedTo P37 FINISHED
Object March 15 incident 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: March 15 incident | Statement: [Peace Preservation Law amendments of 1928, relatedTo, March 15 incident]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: March 15 incident
Context triple: [Peace Preservation Law amendments of 1928, relatedTo, March 15 incident]
  • A. May 15 Incident
    The May 15 Incident was a 1932 coup attempt in Japan in which young naval officers and right-wing extremists assassinated Prime Minister Inukai Tsuyoshi, marking a major step toward militarist rule.
  • B. February 26 Incident
    The February 26 Incident was a 1936 attempted coup d'état in Tokyo led by young Imperial Japanese Army officers seeking to purge the government and military leadership in favor of a more radical, militarist regime.
  • C. January 28 Incident
    The January 28 Incident was a 1932 military conflict in Shanghai between Chinese and Japanese forces that marked a major early clash in the lead-up to the Second Sino-Japanese War.
  • D. September 18 Incident
    The September 18 Incident was a staged 1931 explosion by the Japanese military near Mukden used as a pretext to invade and occupy Manchuria, marking a key escalation in Japanese aggression in China before World War II.
  • E. 31 March Incident
    The 31 March Incident was a 1909 counterrevolutionary uprising in the Ottoman Empire, led by conservative and religious factions in Istanbul against the Young Turk constitutional regime.
  • 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: March 15 incident
Target entity description: The March 15 incident was a major 1928 crackdown in Japan in which authorities arrested thousands of suspected communists and leftists, marking a key escalation in state repression of political dissent.
  • A. May 15 Incident
    The May 15 Incident was a 1932 coup attempt in Japan in which young naval officers and right-wing extremists assassinated Prime Minister Inukai Tsuyoshi, marking a major step toward militarist rule.
  • B. February 26 Incident
    The February 26 Incident was a 1936 attempted coup d'état in Tokyo led by young Imperial Japanese Army officers seeking to purge the government and military leadership in favor of a more radical, militarist regime.
  • C. January 28 Incident
    The January 28 Incident was a 1932 military conflict in Shanghai between Chinese and Japanese forces that marked a major early clash in the lead-up to the Second Sino-Japanese War.
  • D. September 18 Incident
    The September 18 Incident was a staged 1931 explosion by the Japanese military near Mukden used as a pretext to invade and occupy Manchuria, marking a key escalation in Japanese aggression in China before World War II.
  • E. 31 March Incident
    The 31 March Incident was a 1909 counterrevolutionary uprising in the Ottoman Empire, led by conservative and religious factions in Istanbul against the Young Turk constitutional regime.
  • 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_69e2455500788190b4b33030461f3bbd completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17c2cab0881908df1d0629b43d350 completed April 29, 2026, 3:34 a.m.
Created at: April 17, 2026, 3:28 p.m.