Triple
T29080726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Han |
E733972
|
entity |
| Predicate | posthumousNameStyle |
P152147
|
FINISHED |
| Object | Chinese imperial posthumous names |
—
|
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: Chinese imperial posthumous names | Statement: [Emperor of Han, posthumousNameStyle, Chinese imperial posthumous names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousNameStyle Context triple: [Emperor of Han, posthumousNameStyle, Chinese imperial posthumous names]
-
A.
posthumousNameType
chosen
Indicates the specific category or style of a posthumous name assigned to a person after their death.
-
B.
posthumousNameLanguage
Indicates the language in which a person's posthumous name is expressed.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
posthumousTitleOf
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
-
E.
posthumousTitleIn
Indicates that an entity was granted a specific posthumous title within a particular jurisdiction, period, or 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:55 a.m.