Triple
T31251042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenyuan |
E796816
|
entity |
| Predicate | successorEmperorEra |
P198460
|
FINISHED |
| Object | Emperor Shunzong’s Yongzhen era |
—
|
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 Shunzong’s Yongzhen era | Statement: [Zhenyuan, successorEmperorEra, Emperor Shunzong’s Yongzhen era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEmperorEra Context triple: [Zhenyuan, successorEmperorEra, Emperor Shunzong’s Yongzhen era]
-
A.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
-
B.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
C.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
D.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
E.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
| PDg | Predicate description generation | batch_69fee690af688190a845310f102a0c83 |
completed | May 9, 2026, 7:47 a.m. |
Created at: April 29, 2026, 9:11 p.m.