Triple
T29080725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Han |
E733972
|
entity |
| Predicate | templeNameStyle |
P91780
|
FINISHED |
| Object | Chinese imperial temple 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 temple names | Statement: [Emperor of Han, templeNameStyle, Chinese imperial temple names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeNameStyle Context triple: [Emperor of Han, templeNameStyle, Chinese imperial temple names]
-
A.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
B.
templeNameUsage
Indicates how a temple’s name is used or referenced in relation to other entities or contexts.
-
C.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
hasEmperorTempleName
chosen
Indicates that an emperor is associated with a specific posthumous temple name used in imperial ancestral worship.
- 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.