Triple
T18971645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秩父宮雍仁親王 |
E464183
|
entity |
| Predicate | father |
P120
|
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: [秩父宮雍仁親王, father, 大正天皇]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 大正天皇 Context triple: [秩父宮雍仁親王, father, 大正天皇]
-
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.
東久邇宮稔彦王
東久邇宮稔彦王 was a Japanese imperial prince and military officer who briefly served as prime minister of Japan in the immediate aftermath of World War II.
-
C.
久邇宮邦彦王
久邇宮邦彦王 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.
-
D.
仁徳天皇
仁徳天皇は、日本の古代における第16代天皇とされ、大阪府堺市の巨大前方後円墳（仁徳天皇陵古墳）で特に知られる伝説的君主である。
-
E.
常陸宮正仁親王
常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61a8bbc8190881908a71e0f2a53 |
completed | April 20, 2026, 7:30 a.m. |
Created at: April 10, 2026, noon