Triple
T38568589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenpyō-shōhō |
E928297
|
entity |
| Predicate | successorEmperorDuringEra |
P203073
|
FINISHED |
| Object | Emperor Junnin |
—
|
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 Junnin | Statement: [Tenpyō-shōhō, successorEmperorDuringEra, Emperor Junnin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEmperorDuringEra Context triple: [Tenpyō-shōhō, successorEmperorDuringEra, Emperor Junnin]
-
A.
successorEmperorEra
Indicates that one emperor’s era directly follows and succeeds another emperor’s era in chronological order.
-
B.
successorEraUnderSameEmperor
Indicates that one historical era directly follows another while both occur under the reign of the same emperor.
-
C.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
-
D.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
E.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a011c64ff18819099195701bbecbb20 |
completed | May 11, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a011b7f7a508190b2ebb518fb7a2fe9 |
completed | May 10, 2026, 11:57 p.m. |
| PDg | Predicate description generation | batch_6a011c645b68819092ccbb14c1a4c454 |
completed | May 11, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.