Triple

T22031639
Position Surface form Disambiguated ID Type / Status
Subject Jiyun E544100 entity
Predicate relatedWork P37 FINISHED
Object Guangyun NE NERFINISHED

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: Guangyun | Statement: [Jiyun, relatedWork, Guangyun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Guangyun
Context triple: [Jiyun, relatedWork, Guangyun]
  • A. Guangyun chosen
    Guangyun is an 11th-century Chinese rime dictionary that serves as a major source for reconstructing the phonology of Middle Chinese.
  • B. Guangyi
    Guangyi was a warship that served in China's late 19th-century Beiyang Fleet, one of the Qing dynasty's principal modern naval forces.
  • C. Guang
    Guang is the given name of Sima Guang, a renowned Song dynasty historian, scholar, and high-ranking official in imperial China.
  • D. Guangqi
    Guangqi is the given name of Xu Guangqi, a prominent Ming dynasty scholar-official, scientist, and collaborator with Jesuit missionaries in introducing Western science to China.
  • E. Guangqi
    Guangqi was the era name used during part of Emperor Xizong of the Tang dynasty’s reign in late ninth-century China.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127edd5b48190a9aeb2840105c181 completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:24 p.m.