Triple

T3390953
Position Surface form Disambiguated ID Type / Status
Subject Hayam Wuruk E71415 entity
Predicate notableEvent P259 FINISHED
Object Bubat incident
The Bubat incident was a 14th-century political and military clash in the Majapahit Kingdom, marked by the tragic confrontation between Majapahit forces and the Sundanese royal entourage that derailed a planned dynastic marriage and reshaped Javanese inter-kingdom relations.
E353432 NE FINISHED

How this triple was built (4 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: Bubat incident | Statement: [Hayam Wuruk, notableEvent, Bubat incident]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bubat incident
Context triple: [Hayam Wuruk, notableEvent, Bubat incident]
  • A. Musha Incident
    The Musha Incident was a 1930 uprising by Indigenous Seediq people against Japanese colonial rule in Taiwan, marked by a violent attack on Japanese settlers and a brutal military crackdown in response.
  • 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. 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. Jingkang incident
    The Jingkang incident was a pivotal 1127 crisis in Chinese history when Jurchen forces captured the Northern Song capital of Kaifeng and abducted the emperor and his court, leading to the fall of the Northern Song and the establishment of the Southern Song dynasty.
  • E. Tainan Incident of 1915
    The Tainan Incident of 1915, also known as the Tapani Incident, was a major anti-Japanese uprising in colonial Taiwan led by local religious and militia leaders against Japanese rule.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Bubat incident
Triple: [Hayam Wuruk, notableEvent, Bubat incident]
Generated description
The Bubat incident was a 14th-century political and military clash in the Majapahit Kingdom, marked by the tragic confrontation between Majapahit forces and the Sundanese royal entourage that derailed a planned dynastic marriage and reshaped Javanese inter-kingdom relations.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Bubat incident
Target entity description: The Bubat incident was a 14th-century political and military clash in the Majapahit Kingdom, marked by the tragic confrontation between Majapahit forces and the Sundanese royal entourage that derailed a planned dynastic marriage and reshaped Javanese inter-kingdom relations.
  • A. Musha Incident
    The Musha Incident was a 1930 uprising by Indigenous Seediq people against Japanese colonial rule in Taiwan, marked by a violent attack on Japanese settlers and a brutal military crackdown in response.
  • 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. 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. Jingkang incident
    The Jingkang incident was a pivotal 1127 crisis in Chinese history when Jurchen forces captured the Northern Song capital of Kaifeng and abducted the emperor and his court, leading to the fall of the Northern Song and the establishment of the Southern Song dynasty.
  • E. Tainan Incident of 1915
    The Tainan Incident of 1915, also known as the Tapani Incident, was a major anti-Japanese uprising in colonial Taiwan led by local religious and militia leaders against Japanese rule.
  • 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_69ad85a9c4a88190a854019341cb3b60 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb6682c708190b76a7a16cee7c5aa completed March 8, 2026, 5:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3345a95ac819098be25233b8e0ed5 completed March 12, 2026, 9:47 p.m.
NEDg Description generation batch_69b33542a1008190a1cc4aec663d97bc completed March 12, 2026, 9:50 p.m.
NED2 Entity disambiguation (via description) batch_69b3391c4e24819082e9a0f50c1afab8 completed March 12, 2026, 10:07 p.m.
Created at: March 8, 2026, 3:14 p.m.