Triple

T18217013
Position Surface form Disambiguated ID Type / Status
Subject Zhu Changluo E436187 entity
Predicate mother P120 FINISHED
Object Consort Wang 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: Consort Wang | Statement: [Zhu Changluo, mother, Consort Wang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Consort Wang
Context triple: [Zhu Changluo, mother, Consort Wang]
  • A. Consort Wang chosen
    Consort Wang was an imperial consort of the Tang dynasty best known as the mother of Emperor Xianzong.
  • B. Consort Wang
    Consort Wang was an imperial consort of the Ming dynasty’s last ruler, the Chongzhen Emperor, known primarily for her role in the final years of the collapsing dynasty.
  • C. Consort Zheng
    Consort Zheng was a favored imperial consort of the Ming dynasty whose son Zhu Changxun became a prominent prince.
  • D. Consort Guo
    Consort Guo was an imperial consort of Cao Rui, the second emperor of the state of Cao Wei during China’s Three Kingdoms period.
  • E. Consort Guo
    Consort Guo was an imperial consort of the late Tang dynasty best known as the mother of Emperor Xizong of Tang.
  • 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_69d8b9103a8081908bbb0836fef10efd completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e4782db4819093baee57f34be490 completed April 19, 2026, 2:19 p.m.
Created at: April 10, 2026, 10:32 a.m.