Triple
T3376493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 敬宮愛子内親王 |
E71077
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | 皇居（行事参加時など） |
E131323
|
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: [敬宮愛子内親王, residence, 皇居（行事参加時など）]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 皇居（行事参加時など） Context triple: [敬宮愛子内親王, residence, 皇居（行事参加時など）]
-
A.
皇居
chosen
皇居は、日本の天皇と皇室の公的な居所および宮中行事の中心となる東京都千代田区に位置する宮殿・庭園の総称である。
-
B.
Imperial court of Japan (historically)
The historical Imperial court of Japan was the political and cultural center surrounding the emperor, serving as the seat of royal authority, ritual, and literary activity for much of Japanese history.
-
C.
Heian Palace
Heian Palace was the imperial residence and political center of Japan’s Heian period in Kyoto, serving as the seat of the emperor and court from the late 8th to the 12th century.
-
D.
Imperial Palace
The Imperial Palace at Hadrian’s Villa in Tivoli was the opulent residential and administrative complex where Emperor Hadrian and his court lived and governed within the vast estate.
-
E.
皇室典範
皇室典範は、日本の皇位継承や皇族の身分・構成など皇室制度の根幹を定める基本法です。
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e776508190bc123fb17b36f062 |
completed | March 8, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b334465b50819080c6f23eaa6583be |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:13 p.m.