Triple

T15075493
Position Surface form Disambiguated ID Type / Status
Subject Lady Chen E379988 entity
Predicate relative P37 FINISHED
Object Empress Ma E359246 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: Empress Ma | Statement: [Lady Chen, relative, Empress Ma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Empress Ma
Context triple: [Lady Chen, relative, Empress Ma]
  • A. Empress Ma
    Empress Ma was the consort of the Southern Ming Yongli Emperor and a prominent imperial figure during the dynasty’s final resistance against the Qing conquest.
  • B. Empress Ma chosen
    Empress Ma was a prominent imperial consort of early Ming China, best known as the wife of the Hongwu Emperor and a key matriarchal figure in the dynasty’s founding generation.
  • C. Empress He
    Empress He was the empress consort of Emperor Taizu, the founding ruler of China’s Song dynasty.
  • D. Empress He
    Empress He was a Han dynasty empress and influential consort of Emperor Ling of Han, known for her role in the turbulent politics preceding the dynasty’s collapse.
  • E. Empress Xu
    Empress Xu was the principal consort of the Yongle Emperor of the Ming dynasty, noted for her political influence and support of Confucian scholarship at the imperial court.
  • 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dff7fb60448190b454386dd762644d completed April 15, 2026, 8:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69fea5d2765481908f101bef483ed02f completed May 9, 2026, 3:11 a.m.
Created at: April 10, 2026, 3:02 a.m.