Triple

T21685122
Position Surface form Disambiguated ID Type / Status
Subject 米騒動 E535209 entity
Predicate 別名 P39 FINISHED
Object 米騒動事件 NE NERFINISHED

How this triple was built (2 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: 米騒動事件 | Statement: [米騒動, 別名, 米騒動事件]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 米騒動事件
Context triple: [米騒動, 別名, 米騒動事件]
  • A. 米騒動 chosen
    米騒動は1918年に日本各地で発生した米価高騰への民衆の抗議運動であり、政変の引き金ともなった大規模な社会騒擾事件である。
  • B. Sakurada Gate Incident
    The Sakurada Gate Incident was an 1860 assassination of Japanese chief minister Ii Naosuke outside Edo Castle, a pivotal event that intensified political turmoil in the late Tokugawa shogunate.
  • C. Shinjuku Incident
    Shinjuku Incident is a 2009 Hong Kong crime drama film starring Jackie Chan that explores the struggles of Chinese immigrants entangled in the Japanese underworld.
  • D. Akō incident
    The Akō incident was an early 18th-century samurai vendetta in Japan, in which the forty-seven rōnin avenged their lord’s forced seppuku, later becoming a legendary example of loyalty and bushidō.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0c469b6ec8190aee4cadd1527db91 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef96ca668481909f53853c7a8ea811 completed April 27, 2026, 5:03 p.m.
Created at: April 16, 2026, 6:44 p.m.