Triple
T32824155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longshuo |
E839508
|
entity |
| Predicate | emperorPosthumousTitle |
P110011
|
FINISHED |
| Object | Emperor Gaozong 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 Gaozong of Tang | Statement: [Longshuo, emperorPosthumousTitle, Emperor Gaozong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emperorPosthumousTitle Context triple: [Longshuo, emperorPosthumousTitle, Emperor Gaozong of Tang]
-
A.
hasEmperorPosthumousName
Indicates that an individual has been granted or is known by a specific posthumous name used for emperors.
-
B.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
C.
rulingEmperorTempleName
Indicates the temple name assigned to the emperor who is currently ruling.
-
D.
lastEmperorTitle
Indicates that the associated title is the final imperial title held by the last reigning emperor of a given realm or dynasty.
-
E.
posthumousTitleOf
chosen
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.