Triple
T1334830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysanthemum Throne |
E28723
|
entity |
| Predicate | JapaneseName |
P744
|
FINISHED |
| Object | 皇位 |
E55469
|
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: [Chrysanthemum Throne, JapaneseName, 皇位]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 皇位 Context triple: [Chrysanthemum Throne, JapaneseName, 皇位]
-
A.
皇室
皇室 refers to the Imperial House of Japan, the hereditary monarchy that constitutes the world’s oldest continuing royal dynasty.
-
B.
皇居
皇居は、日本の天皇と皇室の公的な居所および宮中行事の中心となる東京都千代田区に位置する宮殿・庭園の総称である。
-
C.
Puyi
Puyi was the last emperor of China and later the puppet ruler of Japanese-controlled Manchukuo during the early 20th century.
-
D.
His Imperial Majesty
chosen
"His Imperial Majesty" is a formal honorific style traditionally used to address or refer to a reigning emperor, particularly in the context of the Holy Roman Empire.
-
E.
Hongxi Emperor
The Hongxi Emperor was a short-reigning early 15th-century ruler of China's Ming dynasty, known for his attempts to reform government and reduce the excesses of his predecessor.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1eb119881909dd5fbf728d9e8ba |
completed | March 1, 2026, 10:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbf3943f88190af908723f87e50e2 |
completed | March 8, 2026, 12:13 a.m. |
Created at: March 1, 2026, 7:55 p.m.