Triple
T37734489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hóngrěn |
E940242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | romanized Chinese given name |
C645
|
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: romanized Chinese given name Context triple: [Hóngrěn, instanceOf, romanized Chinese given name]
-
A.
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.
-
B.
Chinese given name
chosen
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.
-
C.
Chinese dynasty name romanization
A Chinese dynasty name romanization is a standardized Latin-alphabet representation of the original Chinese dynasty name, used to convey its pronunciation and facilitate reference in non-Chinese languages.
-
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.
Japanese given name component
A Japanese given name component is a meaningful unit, often a kanji or syllabic element, that combines with others to form a personal given name and contributes specific semantic or phonetic qualities.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.