Triple
T5904987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 明仁 |
E131321
|
entity |
| Predicate | 別名 |
P39
|
FINISHED |
| Object | 明仁上皇 |
E131321
|
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: [明仁, 別名, 明仁上皇]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 明仁上皇 Context triple: [明仁, 別名, 明仁上皇]
-
A.
明仁
chosen
明仁は、平成時代に在位し日本の象徴として公務に尽力した第125代天皇である。
-
B.
久邇宮邦彦王
久邇宮邦彦王 was a Japanese imperial prince of the Kuni-no-miya house who served as a senior military officer and played a prominent role in the politics and aristocracy of the late Meiji and Taishō periods.
-
C.
睦仁
睦仁 is the personal name of Emperor Meiji, the 122nd emperor of Japan who oversaw the country's rapid modernization and westernization in the late 19th and early 20th centuries.
-
D.
悠仁親王
悠仁親王は、日本の皇室に属する秋篠宮文仁親王と紀子妃の長男であり、皇位継承順位上位に位置する皇族男子である。
-
E.
Prince Iyesato Tokugawa
Prince Iyesato Tokugawa was a prominent Japanese statesman and internationalist leader of the early 20th century who played a key diplomatic role in fostering U.S.–Japan relations and supporting naval disarmament efforts.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c037395a7c8190a44197a5415101f6 |
completed | March 22, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b16ba6c881908e9a909bf86ea92d |
completed | March 23, 2026, 3:20 a.m. |
Created at: March 22, 2026, 3:59 p.m.