Triple

T6350168
Position Surface form Disambiguated ID Type / Status
Subject Daoguang Emperor E142847 entity
Predicate regnalNumberInQing P51882 FINISHED
Object 7th emperor of the Qing dynasty to rule China proper LITERAL 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: 7th emperor of the Qing dynasty to rule China proper | Statement: [Daoguang Emperor, regnalNumberInQing, 7th emperor of the Qing dynasty to rule China proper]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regnalNumberInQing
Context triple: [Daoguang Emperor, regnalNumberInQing, 7th emperor of the Qing dynasty to rule China proper]
  • A. functionInQingDynasty
    Indicates that an entity held a particular official role, position, or function during the Qing Dynasty.
  • B. kangxiRadicalNumber
    Indicates the specific Kangxi radical index number associated with a given Chinese character or component.
  • C. ordinalNumberAsEmperor chosen
    Indicates the numerical order in which a person held the title or role of emperor.
  • D. dynasticNumber
    Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
  • E. eraNumberInJapan
    Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
  • F. None of above.

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_69c008d6dcbc8190aa1c2f1fd8916b42 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067bcec2c8190bb383605847b0f0b completed March 22, 2026, 10:05 p.m.
PD Predicate disambiguation batch_69c060ea1a988190889e47b7e0c819b8 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:31 p.m.