Triple

T14891432
Position Surface form Disambiguated ID Type / Status
Subject Ran E359761 entity
Predicate mainCharacter P1183 FINISHED
Object Taro Ichimonji E1193341 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: Taro Ichimonji | Statement: [Ran, mainCharacter, Taro Ichimonji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taro Ichimonji
Context triple: [Ran, mainCharacter, Taro Ichimonji]
  • A. Toshimichi
    Toshimichi is a Japanese given name most famously borne by Ōkubo Toshimichi, a key statesman and leader of the Meiji Restoration.
  • B. Hidetora Ichimonji chosen
    Hidetora Ichimonji is the aging warlord and tragic protagonist of Akira Kurosawa’s film "Ran," whose attempt to divide his kingdom among his sons leads to betrayal and ruin.
  • C. Tamotsu Takama
    Tamotsu Takama was a Japanese naval officer known for commanding the aircraft carrier Hiryū during World War II.
  • D. Shinnosuke
    Shinnosuke is a character from the Pokémon anime series, known as a young boy appearing in the episode "The Heartbreak of Brock."
  • E. Kuranosuke
    Kuranosuke is the given name of Ōishi Kuranosuke, the historical leader of the Forty-seven rōnin in early 18th-century Japan.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded5f883288190af602633fa7d6860 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffeb7921208190bbf4e1a01c6ec5ee completed May 10, 2026, 2:20 a.m.
Created at: April 10, 2026, 2:10 a.m.