Triple
T28075696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolong |
E709535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese courtesy name |
C46564
|
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: Chinese courtesy name Context triple: [Wolong, instanceOf, Chinese courtesy name]
-
A.
Chinese honorific name
A Chinese honorific name is a formal or respectful appellation, often incorporating titles, virtues, or status markers, used to address or refer to someone with deference in Chinese language and culture.
-
B.
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.
-
C.
traditional Chinese epithet
chosen
A traditional Chinese epithet is a culturally rooted, often honorific or descriptive phrase used to encapsulate a person’s virtues, status, or defining characteristics in a concise, poetic form.
-
D.
Chinese reign era name
A Chinese reign era name is an official title adopted by an emperor to designate and chronologically label a specific period of their rule, used in dating years and historical events.
-
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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:48 p.m.