Triple
T31074028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Zhao |
E791900
|
entity |
| Predicate | successorAsChildEmperor |
P45012
|
FINISHED |
| Object | Liu Long (Emperor Shang of Han) |
—
|
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: Liu Long (Emperor Shang of Han) | Statement: [Liu Zhao, successorAsChildEmperor, Liu Long (Emperor Shang of Han)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsChildEmperor Context triple: [Liu Zhao, successorAsChildEmperor, Liu Long (Emperor Shang of Han)]
-
A.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
B.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
C.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
D.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
E.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: April 29, 2026, 9:01 p.m.