Triple

T9018792
Position Surface form Disambiguated ID Type / Status
Subject Akira Yoshino E215660 entity
Predicate familyName P18 FINISHED
Object Yoshino E612381 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: Yoshino | Statement: [Akira Yoshino, familyName, Yoshino]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yoshino
Context triple: [Akira Yoshino, familyName, Yoshino]
  • A. Yoshino chosen
    Yoshino is a historic mountainous area in Japan renowned for its thousands of cherry trees, religious sites, and role as a major center of Shugendō mountain worship.
  • B. Yamakoshi
    Yamakoshi is a recurring character from the Disney XD sitcom "Pair of Kings," known as a mystical fish with prophetic abilities and a quirky, comedic presence.
  • C. Yamakita
    Yamakita is a rural town in Kanagawa Prefecture, Japan, known for its mountainous terrain, hot springs, and access to outdoor activities such as hiking and river sports.
  • D. Yashio
    Yashio is a city in Saitama Prefecture, Japan, located on the outskirts of Tokyo and functioning largely as a residential commuter town.
  • E. Yashio
    Yashio is a district in Tokyo’s Shinagawa Ward, known primarily as a modern waterfront residential and commercial area.
  • 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_69ca83a38aa88190bf1bb80c4548b5e2 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a4085848190a6aa440e6307e93d completed April 1, 2026, 12:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69d5ffe43c488190b60ea41922211d53 completed April 8, 2026, 7:12 a.m.
Created at: March 30, 2026, 7:07 p.m.