Triple

T13217661
Position Surface form Disambiguated ID Type / Status
Subject Leo Esaki E314661 entity
Predicate familyName P18 FINISHED
Object Esaki 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: Esaki | Statement: [Leo Esaki, familyName, Esaki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Esaki
Context triple: [Leo Esaki, familyName, Esaki]
  • A. Esaki chosen
    Esaki is a Japanese surname most notably associated with physicist Leo Esaki, a Nobel laureate recognized for his pioneering work on quantum tunneling in semiconductors.
  • B. Kamiyama
    Kamiyama is a Japanese surname borne by various individuals, including artists, athletes, and public figures.
  • C. Iwatsuki
    Iwatsuki is a former city in Saitama Prefecture, Japan, now a ward of Saitama City known historically for its traditional doll-making industry.
  • D. Munakata
    Munakata is a coastal city in Japan known for its ancient Munakata Taisha Shinto shrines and its location in northern Fukuoka Prefecture on Kyushu Island.
  • E. Sakae
    Sakae is a major downtown commercial and entertainment district in Nagoya, Japan, known for its shopping, nightlife, and landmark attractions.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98cf392e08190949ee4d194566395 completed April 10, 2026, 11:51 p.m.
Created at: April 9, 2026, 9:18 p.m.