Triple

T28244013
Position Surface form Disambiguated ID Type / Status
Subject Zhaolie Emperor E712110 entity
Predicate posthumousHonorificMeaning P152147 FINISHED
Object Manifest and Ardent 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: Manifest and Ardent | Statement: [Zhaolie Emperor, posthumousHonorificMeaning, Manifest and Ardent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: posthumousHonorificMeaning
Context triple: [Zhaolie Emperor, posthumousHonorificMeaning, Manifest and Ardent]
  • A. posthumousForm
    Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
  • B. posthumousTitleIn
    Indicates that an entity was granted a specific posthumous title within a particular jurisdiction, period, or context.
  • C. posthumousTitleOf
    Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
  • D. posthumousNameType chosen
    Indicates the specific category or style of a posthumous name assigned to a person after their death.
  • E. posthumousAssociation
    Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
  • 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_69efb51fb98881909692421959ec0170 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a931748190a637e631a52bbfaa completed May 2, 2026, 7:34 p.m.
Created at: April 27, 2026, 11 p.m.