Triple
T23408700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dezong |
E560005
|
entity |
| Predicate | posthumousNameType |
P152147
|
FINISHED |
| Object | temple name |
—
|
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 name | Statement: [Dezong, posthumousNameType, temple name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousNameType Context triple: [Dezong, posthumousNameType, temple name]
-
A.
posthumousTitleOf
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
-
B.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
C.
posthumousTitleYear
Indicates the year in which an entity was formally granted a title or honor after its death.
-
D.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
-
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. 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:38 p.m.