Triple

T21317947
Position Surface form Disambiguated ID Type / Status
Subject Tomioka E525527 entity
Predicate hasNotableBearer P458 FINISHED
Object Tomioka Sadako 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: Tomioka Sadako | Statement: [Tomioka, hasNotableBearer, Tomioka Sadako]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tomioka Sadako
Context triple: [Tomioka, hasNotableBearer, Tomioka Sadako]
  • A. Sadako chosen
    Sadako is a feminine Japanese given name commonly associated with several notable historical and fictional figures.
  • B. Yoshiko
    Yoshiko is a feminine Japanese given name commonly used across various generations and often associated with traditional Japanese culture.
  • C. Sachiko
    Sachiko is a Japanese feminine given name that can be written with various kanji combinations, often conveying meanings related to happiness or child.
  • D. Shigeko
    Shigeko is a Japanese feminine given name that has been borne by various notable women, including members of the imperial family.
  • E. Toshiko Soma
    Toshiko Soma was the Japanese wife of Indian revolutionary Rashbehari Bose, known for supporting his anti-colonial activities while he lived in Japan.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dd1ce9c81908c373362254427bf completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 4:36 p.m.