Triple

T15990148
Position Surface form Disambiguated ID Type / Status
Subject Yee E387802 entity
Predicate hasAlternativeSpelling P457 FINISHED
Object Yue E172883 NE FINISHED

How this triple was built (2 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: Yue | Statement: [Yee, hasAlternativeSpelling, Yue]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yue
Context triple: [Yee, hasAlternativeSpelling, Yue]
  • A. Yue chosen
    Yue is a given name that appears in various East Asian cultures, often associated with meanings like "moon" or "delight" depending on the characters used.
  • B. Tian
    Tian is a Chinese given name commonly used for both males and females, often associated with meanings related to "sky" or "heaven."
  • C. Siyi Yue
    Siyi Yue is a regional variety of Yue Chinese spoken primarily in the Siyi (Four Counties) area of Guangdong, China.
  • D. 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.
  • E. Qiyu
    Qiyu was the personal name of the Jingtai Emperor, a 15th-century ruler of China's Ming dynasty.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157829ec08190aa4a683e29a0148a completed April 16, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3d2369081909efa2d4addf0cf2d completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:54 a.m.