Triple

T11270396
Position Surface form Disambiguated ID Type / Status
Subject Emperor Monmu E266795 entity
Predicate father P120 FINISHED
Object Prince Kusakabe E716693 NE FINISHED

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: Prince Kusakabe | Statement: [Emperor Monmu, father, Prince Kusakabe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prince Kusakabe
Context triple: [Emperor Monmu, father, Prince Kusakabe]
  • A. Prince Kusakabe chosen
    Prince Kusakabe was a Japanese imperial prince of the Asuka period, known primarily as the son of Emperor Tenmu and Empress Jitō and the father of Empress Genmei.
  • B. Prince Ōtomo
    Prince Ōtomo was a Japanese imperial prince of the Asuka period who briefly served as crown prince and de facto ruler before his defeat and death in the Jinshin War of 672.
  • C. Yoshitsugu
    Yoshitsugu is a Japanese given name commonly used for males.
  • D. Prince Uimin
    Prince Uimin was a Korean royal prince of the Joseon dynasty and the Korean Empire, known as a younger son of Emperor Gojong and a key figure in the final years of Korea’s monarchy under Japanese rule.
  • E. Prince Takamado
    Prince Takamado was a member of the Japanese imperial family known for his diplomatic work, promotion of international cultural exchange, and support for sports, especially soccer.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9506204819089dc0827483bd948 completed April 9, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_69e542c5fdb88190968831279eaeea49 completed April 19, 2026, 9:01 p.m.
Created at: April 8, 2026, 9:31 p.m.