Triple
T15286569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuanzong |
E365415
|
entity |
| Predicate | honorificTitleType |
P94747
|
FINISHED |
| Object | temple name of Chinese emperor |
—
|
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 of Chinese emperor | Statement: [Xuanzong, honorificTitleType, temple name of Chinese emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificTitleType Context triple: [Xuanzong, honorificTitleType, temple name of Chinese emperor]
-
A.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
B.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
C.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
-
D.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
E.
hasHonorificType
chosen
Indicates that an entity is associated with a specific type or category of honorific title or form of address.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e551bb0819094db097285443740 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.