Triple
T6897201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Kōmei |
E159399
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 孝明天皇 |
E557094
|
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 Kōmei, nativeName, 孝明天皇]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 孝明天皇 Context triple: [Emperor Kōmei, nativeName, 孝明天皇]
-
A.
孝明天皇
chosen
孝明天皇は、幕末の動乱期に在位し、尊王攘夷運動や公武合体政策の中心となった日本の第121代天皇である。
-
B.
Emperor Sanjō
Emperor Sanjō was the 67th emperor of Japan, a Heian-period monarch whose reign was marked by the political dominance of the Fujiwara regents.
-
C.
明仁
明仁は、平成時代に在位し日本の象徴として公務に尽力した第125代天皇である。
-
D.
Emperor Go-Toba
Emperor Go-Toba was a late 12th- to early 13th-century Japanese emperor known for his cultural patronage, especially of poetry, and for leading the failed Jōkyū War against the Kamakura shogunate.
-
E.
Emperor Go-Sanjō
Emperor Go-Sanjō was the 71st emperor of Japan, known for his efforts to strengthen imperial authority and reform the administration during the late Heian period.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95c44a48190876d62749411bbb6 |
completed | March 27, 2026, 7:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748e5182c81908ed01d1091933d09 |
completed | March 28, 2026, 3:20 a.m. |
Created at: March 27, 2026, 2:24 p.m.