Triple

T9712127
Position Surface form Disambiguated ID Type / Status
Subject Yan (surname) E235045 entity
Predicate canBeWrittenAs P12679 FINISHED
Object 閻
閻 is a traditional Chinese surname character, commonly romanized as Yan and used in Chinese-speaking communities.
 E816898 NE FINISHED

How this triple was built (4 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 閻 | Statement: [Yan (surname), canBeWrittenAs, 閻]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 閻
Context triple: [Yan (surname), canBeWrittenAs, 閻]
  • A. Yih
    Yih is the surname of Chia-Shun Yih, a notable Chinese-American engineer and fluid dynamicist.
  • B. Yu
    Yu was the personal name of Emperor Daizong, a ruler of China's Tang dynasty in the 8th century.
  • C. Yüeh
    Yüeh is an alternative romanization of "Yue," a term historically associated with various ancient peoples and regions in southern China and their related languages and cultures.
  • D. Ying
    Ying was the principal political and cultural center of the ancient Chinese State of Chu during the Zhou dynasty period.
  • E. Zhenyuan
    Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 閻
Triple: [Yan (surname), canBeWrittenAs, 閻]
Generated description
閻 is a traditional Chinese surname character, commonly romanized as Yan and used in Chinese-speaking communities.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: 閻
Target entity description: 閻 is a traditional Chinese surname character, commonly romanized as Yan and used in Chinese-speaking communities.
  • A. Yih
    Yih is the surname of Chia-Shun Yih, a notable Chinese-American engineer and fluid dynamicist.
  • B. Yu
    Yu was the personal name of Emperor Daizong, a ruler of China's Tang dynasty in the 8th century.
  • C. Yüeh
    Yüeh is an alternative romanization of "Yue," a term historically associated with various ancient peoples and regions in southern China and their related languages and cultures.
  • D. Ying
    Ying was the principal political and cultural center of the ancient Chinese State of Chu during the Zhou dynasty period.
  • E. Zhenyuan
    Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
  • F. None of above. chosen

Provenance (5 batches)

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_69ca84cd8fa0819090a5e243ceb37003 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e0705f8819095852263009c28c5 completed April 1, 2026, 10:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f8c26dc8190a6fa21bde27ba6fa completed April 4, 2026, 11:32 p.m.
NEDg Description generation batch_69d1a0326dd081909e39e422c11cc08f completed April 4, 2026, 11:35 p.m.
NED2 Entity disambiguation (via description) batch_69d1a0c05aa88190a93b0b71bef5c417 completed April 4, 2026, 11:37 p.m.
Created at: March 30, 2026, 8:19 p.m.