Triple

T15383107
Position Surface form Disambiguated ID Type / Status
Subject Yasuko Miyamoto E367850 entity
Predicate givenName P17 FINISHED
Object Yasuko E713441 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: Yasuko | Statement: [Yasuko Miyamoto, givenName, Yasuko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yasuko
Context triple: [Yasuko Miyamoto, givenName, Yasuko]
  • A. Yasuko chosen
    Yasuko is a feminine Japanese given name commonly used for women.
  • B. Yoshihime
    Yoshihime was a Sengoku-period Japanese noblewoman best known as the mother of the powerful warlord Date Masamune.
  • C. Hisako, Princess Takamado
    Hisako, Princess Takamado is a member of the Japanese imperial family known for her extensive work in cultural exchange, sports promotion, and various charitable and artistic activities.
  • D. Yuriko
    Yuriko is the given name of Japanese actress Rinko Kikuchi, known for her roles in films such as "Babel" and "Pacific Rim."
  • E. Nagako Kuni
    Nagako Kuni, later known as Empress Kōjun, was the wife of Emperor Shōwa (Hirohito) and the longest-serving empress consort in Japanese history.
  • 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_69d85a1551a08190ba2caea7cd51c639 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e7397188190bde42b897ab4b5b4 completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a6b67c08190b0df6b9fd65ff28b completed May 9, 2026, 11:28 a.m.
Created at: April 10, 2026, 3:19 a.m.