Triple
T15394717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Xiaojing |
E368142
|
entity |
| Predicate | templeNameUsage |
P118620
|
FINISHED |
| Object | used in ancestral temple rites |
—
|
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: used in ancestral temple rites | Statement: [Emperor Xiaojing, templeNameUsage, used in ancestral temple rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeNameUsage Context triple: [Emperor Xiaojing, templeNameUsage, used in ancestral temple rites]
-
A.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
B.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
templeAlsoHonors
Indicates that a temple, in addition to its primary dedication, honors or venerates another deity, figure, or sacred subject.
-
D.
shrineName
Indicates that an entity has the specified name of a shrine.
-
E.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.