Triple
T36068539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toba |
E1043299
|
entity |
| Predicate | successorAsCloisteredEmperor |
P202057
|
FINISHED |
| Object | Emperor Go-Shirakawa |
—
|
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 Go-Shirakawa | Statement: [Toba, successorAsCloisteredEmperor, Emperor Go-Shirakawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsCloisteredEmperor Context triple: [Toba, successorAsCloisteredEmperor, Emperor Go-Shirakawa]
-
A.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
B.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
C.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
D.
successorAsLatinEmperor
Indicates that one entity became the next holder of the title of Latin Emperor after another entity.
-
E.
successorAsKingOfTheRomans
Indicates that one person is the next holder of the title "King of the Romans" following another person in the line of succession.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
| PDg | Predicate description generation | batch_6a004a87bb908190a2bd164a60245f1d |
completed | May 10, 2026, 9:06 a.m. |
Created at: May 3, 2026, 4:08 p.m.