Triple

T28244014
Position Surface form Disambiguated ID Type / Status
Subject Zhaolie Emperor E712110 entity
Predicate posthumousHonorificType P152147 FINISHED
Object temple and posthumous style combined 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: temple and posthumous style combined | Statement: [Zhaolie Emperor, posthumousHonorificType, temple and posthumous style combined]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: posthumousHonorificType
Context triple: [Zhaolie Emperor, posthumousHonorificType, temple and posthumous style combined]
  • A. posthumousNameType chosen
    Indicates the specific category or style of a posthumous name assigned to a person after their death.
  • B. posthumousTitleOf
    Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
  • C. honourType
    Indicates the specific category or classification of an honour or award associated with an entity.
  • D. posthumousTitleIn
    Indicates that an entity was granted a specific posthumous title within a particular jurisdiction, period, or context.
  • E. honorificType
    Indicates the type or category of honorific or formal title associated with an entity in a given context.
  • 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_69f65876c52c8190bc889c7a67bd07f3 completed May 2, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69f6575d89788190aca478e4aea05a65 completed May 2, 2026, 7:58 p.m.
Created at: April 27, 2026, 11 p.m.