Triple

T1575952
Position Surface form Disambiguated ID Type / Status
Subject Taro E33651 entity
Predicate instanceOf P0 FINISHED
Object Japanese masculine given name C7377 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 masculine given name
Context triple: [Taro, instanceOf, Japanese masculine given name]
  • A. Japanese given name chosen
    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. masculine given name
    A masculine given name is a personal name traditionally assigned to individuals identified as male, often reflecting cultural, historical, or familial significance.
  • C. English masculine given name
    An English masculine given name is a personal first name traditionally used for boys and men in English-speaking cultures, often derived from historical, biblical, or linguistic roots specific to the English language.
  • D. 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.
  • E. Chinese given name
    A Chinese given name is a personal name, typically one or two characters long, chosen to convey specific meanings, virtues, or aspirations, and used after the family name in Chinese naming conventions.
  • F. None of above.

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_69a885f27a4c8190a4622252cdf54c00 completed March 4, 2026, 7:20 p.m.
Created at: March 4, 2026, 7:27 p.m.