Triple

T29357747
Position Surface form Disambiguated ID Type / Status
Subject Guanghe E744491 entity
Predicate eraSequenceInEmperorLingReign P166676 FINISHED
Object after Jianning and before Zhongping 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: after Jianning and before Zhongping | Statement: [Guanghe, eraSequenceInEmperorLingReign, after Jianning and before Zhongping]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eraSequenceInEmperorLingReign
Context triple: [Guanghe, eraSequenceInEmperorLingReign, after Jianning and before Zhongping]
  • A. eraSequenceWithinDynasty
    Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
  • B. eraNumberUnderEmperorYang
    Indicates that the specified era name or era number was used during the reign of Emperor Yang.
  • C. eraSequenceInNorthernQi
    Indicates that one era chronologically follows another within the historical context of the Northern Qi dynasty.
  • D. eraNumberInDynasty
    Indicates that a specific era is identified by and associated with a particular numbered position within a dynasty.
  • E. ordinalNumberAsEmperor
    Indicates the numerical order in which a person held the title or role of emperor.
  • F. None of above. chosen

Provenance (4 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66985cdf881909808aaca2394310d completed May 2, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
PDg Predicate description generation batch_69f661b47d088190934f63884a203261 completed May 2, 2026, 8:42 p.m.
Created at: April 28, 2026, 2:14 p.m.