Triple
T5904986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 明仁 |
E131321
|
entity |
| Predicate | 別名 |
P39
|
FINISHED |
| Object | 今上天皇 |
E153012
|
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.
Tennō Tanjōbi
Tennō Tanjōbi is Japan’s national holiday celebrating the reigning emperor’s birthday, observed on a date that changes with each new emperor.
-
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.
悠仁親王
悠仁親王は、日本の皇室に属する秋篠宮文仁親王と紀子妃の長男であり、皇位継承順位上位に位置する皇族男子である。
-
D.
Tennō
chosen
Tennō is the Japanese term for the Emperor of Japan, regarded as the ceremonial and symbolic monarch and, in tradition, a descendant of the sun goddess Amaterasu.
-
E.
His Majesty The Emperor
His Majesty The Emperor is the reigning male sovereign of an empire, serving as its highest hereditary monarch and head of state.
- 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.