Triple
T21639470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 仙洞御所 |
E534051
|
entity |
| Predicate | adjacentTo |
P224
|
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: [仙洞御所, adjacentTo, 京都御所]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 京都御所 Context triple: [仙洞御所, adjacentTo, 京都御所]
-
A.
院御所
院御所 refers to the retired emperor’s residence and political base in Kyoto during the insei (cloistered rule) period of Japan.
-
B.
Kyoto Imperial Palace
chosen
Kyoto Imperial Palace is the historic former seat of Japan’s emperors in Kyoto, renowned for its traditional architecture and role as the center of imperial court life before the capital moved to Tokyo.
-
C.
大宮御所
大宮御所は、京都御苑内に位置し、かつての皇太后や上皇后の御所として用いられた日本の皇室関連施設である。
-
D.
敬宮
敬宮 is the courtesy name of Princess Aiko, the only child of Emperor Naruhito and Empress Masako of Japan.
-
E.
Tokyo Imperial Palace
Tokyo Imperial Palace is the primary residence and administrative center of Japan’s imperial family, located in a large historic park area in central Tokyo.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5390ba7481908f58230779e5b7bb |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 16, 2026, 6:35 p.m.