Triple

T37120624
Position Surface form Disambiguated ID Type / Status
Subject nosuke E919239 entity
Predicate instanceOf P0 FINISHED
Object Japanese given name component C65123 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: Japanese given name component
Context triple: [nosuke, instanceOf, Japanese given name component]
  • A. Japanese given name
    A Japanese given name is a personal name assigned at birth or during naming ceremonies in Japan, typically written in kanji, hiragana, or katakana, and often chosen for its meaning, sound, and cultural significance.
  • B. Japanese honorific name
    A Japanese honorific name is a personal name accompanied by a respectful suffix (such as -san, -sama, -kun, or -chan) that reflects the social relationship, status, and level of politeness between speaker and referent.
  • C. Korean given name
    A Korean given name is a personal name, typically consisting of two syllables written in Hangul (and sometimes Hanja), chosen to convey specific meanings, virtues, or aspirations for the individual.
  • D. Japanese place name
    A Japanese place name is a toponym used to identify a specific geographic location in Japan, often reflecting historical, cultural, or natural features through kanji characters and traditional naming conventions.
  • E. romanized Japanese name
    A romanized Japanese name is a personal name of Japanese origin written using the Latin alphabet according to a specific romanization system.
  • F. None of above. chosen

Provenance (1 batch)

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_69f76e9c57148190ba789dd059645bb9 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:15 p.m.