Triple

T29043896
Position Surface form Disambiguated ID Type / Status
Subject Shin E738078 entity
Predicate instanceOf P0 FINISHED
Object Japanese masculine given name element 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 element
Context triple: [Shin, instanceOf, Japanese masculine given name element]
  • 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. Indian masculine given name
    An Indian masculine given name is a personal first name traditionally assigned to males in India, often reflecting cultural, religious, linguistic, or familial significance.
  • E. 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.
  • 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_69f077efb3848190b41574e1670f6ae2 completed April 28, 2026, 9:03 a.m.
Created at: April 28, 2026, 10:03 a.m.