Triple
T33674353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Huizhao Xiaode |
E862717
|
entity |
| Predicate | linkedRulerTempleName |
P195701
|
FINISHED |
| Object | Emperor Wuzong of Tang |
—
|
NE NERFINISHED |
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: Emperor Wuzong of Tang | Statement: [Emperor Huizhao Xiaode, linkedRulerTempleName, Emperor Wuzong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerTempleName Context triple: [Emperor Huizhao Xiaode, linkedRulerTempleName, Emperor Wuzong of Tang]
-
A.
lastRulerTempleName
Indicates the name of the temple associated with the most recent or final ruler in a given context.
-
B.
linkedTempleDeity
Indicates a relationship where a temple is associated with, or dedicated to, a particular deity.
-
C.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: May 1, 2026, 1:43 a.m.