Triple
T22533513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 牧野伸顕 |
E557100
|
entity |
| Predicate | 仕えた君主 |
P148552
|
FINISHED |
| Object | 大正天皇 |
—
|
NE NERFINISHED |
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.
Emperor Taishō
chosen
Emperor Taishō was the 123rd emperor of Japan, whose reign from 1912 to 1926 marked a period of continued modernization and growing parliamentary democracy known as "Taishō democracy."
-
B.
上皇明仁
上皇明仁は、平成時代に在位した第125代天皇であり、2019年に生前退位して上皇となった日本の前天皇である。
-
C.
東久邇宮稔彦王
東久邇宮稔彦王 was a Japanese imperial prince and military officer who briefly served as prime minister of Japan in the immediate aftermath of World War II.
-
D.
久邇宮邦彦王
久邇宮邦彦王 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.
-
E.
三笠宮崇仁親王
三笠宮崇仁親王は、大正天皇の第四皇子であり、昭和から平成にかけて長く存命した日本の皇族で、歴史学者としても知られた人物である。
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 16, 2026, 8:51 p.m.