Triple
T22440234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秋篠宮紀子妃 |
E554734
|
entity |
| Predicate | 居住地 |
P24950
|
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.
赤坂御用地
chosen
赤坂御用地は、東京都港区赤坂に位置する日本の皇室関連施設が集まる広大な御用地で、皇族方の御所や宮邸が置かれているエリアである。
-
B.
Aoyama Palace, Tokyo, Japan
Aoyama Palace in Tokyo, Japan, was a former imperial residence best known as the birthplace and early home of Emperor Taishō.
-
C.
東京都千代田区の日比谷公会堂
東京都千代田区の日比谷公会堂は、東京・日比谷公園内に位置する歴史ある公会堂で、政治集会や演説会、文化イベントの会場として知られる建築物である。
-
D.
大宮御所
大宮御所は、京都御苑内に位置し、かつての皇太后や上皇后の御所として用いられた日本の皇室関連施設である。
-
E.
院御所
院御所 refers to the retired emperor’s residence and political base in Kyoto during the insei (cloistered rule) period of Japan.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae0edcc8190919b198035de0df2 |
completed | April 29, 2026, 1:12 a.m. |
Created at: April 16, 2026, 8:47 p.m.