Triple
T37879737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōnin |
E944837
|
entity |
| Predicate | eraNameForEmperor |
P189322
|
FINISHED |
| Object | Emperor Go-Hanazono |
—
|
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-Hanazono | Statement: [Ōnin, eraNameForEmperor, Emperor Go-Hanazono]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameForEmperor Context triple: [Ōnin, eraNameForEmperor, Emperor Go-Hanazono]
-
A.
hasEmperorPosthumousName
Indicates that an individual has been granted or is known by a specific posthumous name used for emperors.
-
B.
rulingEmperorTempleName
Indicates the temple name assigned to the emperor who is currently ruling.
-
C.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
D.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
E.
hasEmperorTempleName
Indicates that an emperor is associated with a specific posthumous temple name used in imperial ancestral worship.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.