Triple

T15290705
Position Surface form Disambiguated ID Type / Status
Subject Jingtai Emperor E365518 entity
Predicate personalName P24312 FINISHED
Object Qiyu E365518 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: Qiyu | Statement: [Jingtai Emperor, personalName, Qiyu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qiyu
Context triple: [Jingtai Emperor, personalName, Qiyu]
  • A. Qiyu chosen
    Qiyu was the personal name of the Jingtai Emperor, a 15th-century ruler of China's Ming dynasty.
  • B. Jingyu
    Jingyu is a Chinese given name that can be used for people of any gender and carries various meanings depending on the characters used to write it.
  • C. Tian
    Tian is a Chinese given name commonly used for both males and females, often associated with meanings related to "sky" or "heaven."
  • D. Huayu
    Huayu is a term used primarily in Singapore, Malaysia, and other overseas Chinese communities to refer to the standardized form of Mandarin Chinese used in education and media.
  • E. Yue
    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.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03680b60c8190a3ea54a9d34c8105 completed April 16, 2026, 1:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69feef7d4da4819080f101c3a525ea11 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:15 a.m.