Triple
T5968009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hitachi |
E132800
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object |
常陸宮正仁親王
常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
|
E563401
|
NE FINISHED |
How this triple was built (4 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: [Prince Hitachi, nativeName, 常陸宮正仁親王]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 常陸宮正仁親王 Context triple: [Prince Hitachi, nativeName, 常陸宮正仁親王]
-
A.
秩父宮 雍仁親王
秩父宮 雍仁親王 was a Japanese imperial prince, younger brother of Emperor Shōwa (Hirohito), known for his military career and role in early Shōwa-era politics.
-
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.
秋篠宮
秋篠宮は、日本の皇室に属する皇嗣であり、天皇徳仁の弟にあたる皇族男性である。
-
E.
Prince Higashifushimi Yorihito
Prince Higashifushimi Yorihito was a Japanese imperial prince and high-ranking naval officer who became one of the most senior leaders in the Imperial Japanese Navy.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 常陸宮正仁親王 Triple: [Prince Hitachi, nativeName, 常陸宮正仁親王]
Generated description
常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 常陸宮正仁親王 Target entity description: 常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
-
A.
秩父宮 雍仁親王
秩父宮 雍仁親王 was a Japanese imperial prince, younger brother of Emperor Shōwa (Hirohito), known for his military career and role in early Shōwa-era politics.
-
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.
秋篠宮
秋篠宮は、日本の皇室に属する皇嗣であり、天皇徳仁の弟にあたる皇族男性である。
-
E.
Prince Higashifushimi Yorihito
Prince Higashifushimi Yorihito was a Japanese imperial prince and high-ranking naval officer who became one of the most senior leaders in the Imperial Japanese Navy.
- F. None of above. chosen
Provenance (5 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03a3f612481908744cb645f2ede1d |
completed | March 22, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113585ad88190a35d549448b10def |
completed | March 23, 2026, 10:18 a.m. |
| NEDg | Description generation | batch_69c113de5d788190affa46cf416d180d |
completed | March 23, 2026, 10:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c1144e77f881908ab59a67160c1630 |
completed | March 23, 2026, 10:22 a.m. |
Created at: March 22, 2026, 4:03 p.m.