Triple
T13635893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Go-Shirakawa |
E325847
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 後白河天皇 |
E325847
|
NE FINISHED |
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: 後白河天皇 | Statement: [Emperor Go-Shirakawa, nativeName, 後白河天皇]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 後白河天皇 Context triple: [Emperor Go-Shirakawa, nativeName, 後白河天皇]
-
A.
仁徳天皇
仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳（仁徳天皇陵古墳）で特に知られる伝説的君主である。
-
B.
孝明天皇
孝明天皇は、幕末の動乱期に在位し、尊王攘夷運動や公武合体政策の中心となった日本の第121代天皇である。
-
C.
Emperor Go-Shirakawa
chosen
Emperor Go-Shirakawa was a 12th-century Japanese emperor whose turbulent reign and subsequent cloistered rule marked a pivotal period of political conflict and transition in the late Heian era.
-
D.
成子内親王
成子内親王は、日本の皇族として生まれた内親王で、皇室の血筋を引く女性皇族の一人である。
-
E.
Emperor Shirakawa
Emperor Shirakawa was a Japanese sovereign of the late 11th and early 12th centuries who is renowned for pioneering the system of cloistered rule that shaped Heian-period politics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.