Triple
T15120982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小室眞子 |
E361170
|
entity |
| Predicate | 別名 |
P39
|
FINISHED |
| Object | 眞子内親王 |
E554735
|
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.
眞子内親王
chosen
眞子内親王は、日本の皇族で秋篠宮文仁親王と紀子妃の長女として知られる元内親王である。
-
B.
佳子内親王
佳子内親王は、日本の秋篠宮文仁親王と紀子妃の次女であり、現代的な感性や公的活動で注目を集める日本の皇族女性である。
-
C.
敬宮愛子内親王
敬宮愛子内親王 is the only child of Emperor Naruhito and Empress Masako of Japan and a member of the Japanese imperial family.
-
D.
Kiko, Crown Princess Akishino
Kiko, Crown Princess Akishino is a member of the Japanese imperial family who serves as the wife of Crown Prince Fumihito and is known for her public service and involvement in social and cultural activities in Japan.
-
E.
Michiko, Crown Princess of Japan
Michiko, Crown Princess of Japan, later Empress Michiko, is the first commoner to marry into the Japanese imperial family and a widely respected figure known for her modernizing influence and compassionate public presence.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059f69a881909929a037a0eef702 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd24523081908cf12a5d6bdd634d |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:06 a.m.