Triple

T18582790
Position Surface form Disambiguated ID Type / Status
Subject Zunhua City E454157 entity
Predicate hasName P744 FINISHED
Object Zunhua 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: Zunhua | Statement: [Zunhua City, hasName, Zunhua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zunhua
Context triple: [Zunhua City, hasName, Zunhua]
  • A. Zhongmou
    Zhongmou is the courtesy name of Sun Quan, the founding emperor of Eastern Wu during China’s Three Kingdoms period.
  • B. Yuncheng
    Yuncheng is a major city in southern Shanxi Province, China, known for its historical sites and role as a regional transportation and economic hub.
  • C. Zicheng
    Zicheng is the courtesy name of Zeng Guofan, a prominent Qing dynasty statesman, military leader, and Confucian scholar who played a key role in suppressing the Taiping Rebellion.
  • D. Huizheng
    Huizheng was the father of Empress Dowager Cixi, the powerful de facto ruler of late Qing dynasty China.
  • E. Zunhua City chosen
    Zunhua City is a county-level city in northeastern Hebei Province, China, known for its historical sites and administrative affiliation with the prefecture-level city of Tangshan.
  • 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_69d8d38ae7e081908a98df1251842402 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e543d10b1c8190a401df810b7290c9 completed April 19, 2026, 9:06 p.m.
Created at: April 10, 2026, 11:44 a.m.