Triple

T947119
Position Surface form Disambiguated ID Type / Status
Subject Manchukuo E20436 entity
Predicate hadEvent P22468 FINISHED
Object Mukden Incident E79325 NE FINISHED

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: Mukden Incident | Statement: [Manchukuo, hadEvent, Mukden Incident]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mukden Incident
Context triple: [Manchukuo, hadEvent, Mukden Incident]
  • A. Mukden Incident chosen
    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.
  • B. 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.
  • 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. Wushe Incident
    The Wushe Incident was a 1930 armed uprising by the Seediq indigenous people against Japanese colonial authorities in central Taiwan, marking one of the most significant anti-colonial rebellions during Japanese rule.
  • E. Xi’an Incident
    The Xi’an Incident was a 1936 political crisis in which Nationalist leader Chiang Kai-shek was detained by his own generals, forcing him to agree to a united front with the Chinese Communists against Japanese aggression.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadEvent
Context triple: [Manchukuo, hadEvent, Mukden Incident]
  • A. hadListeningEventAt
    Indicates that a listening event involving an entity occurred at a specific time or place.
  • B. hasAct
    Indicates that an entity performs, participates in, or is associated with a specific act or action.
  • C. hadMember
    Indicates that an entity was formerly a member or part of another entity or group.
  • D. hadFort
    Indicates that an entity possessed, controlled, or contained a fort at some time.
  • E. hasDam
    Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
  • F. None of above. chosen

Provenance (5 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_69a493b0f2fc81908cd227480a5356a1 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3be19448190a8863fce3d152430 completed March 1, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a933a643708190a8d3da54b1e91bcf completed March 5, 2026, 7:41 a.m.
PD Predicate disambiguation batch_69a4b29f05f481908814bd11f235e9d0 completed March 1, 2026, 9:41 p.m.
PDg Predicate description generation batch_69a4b385176081909e3e8c3f647c1fd4 completed March 1, 2026, 9:45 p.m.
Created at: March 1, 2026, 7:40 p.m.