Triple

T17006578
Position Surface form Disambiguated ID Type / Status
Subject Chen dynasty E412585 entity
Predicate eraName P2938 FINISHED
Object Taijian (later) E1244493 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: Taijian (later)  | Statement: [Chen dynasty, eraName, Taijian (later) ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taijian (later) 
Context triple: [Chen dynasty, eraName, Taijian (later) ]
  • A. Taijian chosen
    Taijian was a historical Chinese era name used during the Chen dynasty, marking a specific reign period in its imperial chronology.
  • B. Yingtian
    Yingtian was an important early Ming dynasty capital city, historically centered around present-day Nanjing in China.
  • C. Jianzhong
    Jianzhong was a brief imperial era name used during the reign of Emperor Dezong in the Tang dynasty, marking a specific period in his rule.
  • D. Shaowu
    Shaowu is a county-level city in northwestern Fujian Province, China, known for its mountainous landscape and location along the upper reaches of the Min River.
  • E. Yujian
    Yujian was the personal name of the Longwu Emperor, a short-lived Ming dynasty claimant who resisted the Qing conquest in southern China.
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d3831268819089286053a5acf653 completed April 18, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b46e89c81908271eb22b535c558 completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:32 a.m.