Triple
T17128306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Go-Ichijō |
E415654
|
entity |
| Predicate | titleInJapanese |
P4863
|
FINISHED |
| Object | 後一条天皇 |
E1253054
|
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-Ichijō, titleInJapanese, 後一条天皇]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 後一条天皇 Context triple: [Emperor Go-Ichijō, titleInJapanese, 後一条天皇]
-
A.
後一条天皇
chosen
後一条天皇 was the 68th emperor of Japan, a Heian-period monarch who reigned in the early 11th century and was known for his short life and largely ceremonial rule under powerful regent families.
-
B.
後陽成天皇
後陽成天皇 was a late 16th- to early 17th-century Japanese emperor of the Azuchi–Momoyama and early Edo periods, whose reign overlapped with the unification of Japan under Oda Nobunaga, Toyotomi Hideyoshi, and Tokugawa Ieyasu.
-
C.
孝明天皇
孝明天皇は、幕末の動乱期に在位し、尊王攘夷運動や公武合体政策の中心となった日本の第121代天皇である。
-
D.
仁徳天皇
仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳（仁徳天皇陵古墳）で特に知られる伝説的君主である。
-
E.
藤原頼通
藤原頼通は、平安時代中期に摂政・関白として長期にわたり政権を掌握し、藤原氏全盛期を築いた公卿である。
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f0285a408190ae5e4c4679c07fbf |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01482af1288190b7fdc8a84d0edeaf |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:36 a.m.