Triple
T14284829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 港区 |
E354141
|
entity |
| Predicate | hasBusinessDistrict |
P459
|
FINISHED |
| Object | 赤坂 |
E1090342
|
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: [港区, hasBusinessDistrict, 赤坂]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 赤坂 Context triple: [港区, hasBusinessDistrict, 赤坂]
-
A.
赤坂
chosen
赤坂は、東京都港区に位置し、官公庁や高級ホテル、飲食店が集まるビジネス・商業エリアとして知られる街です。
-
B.
赤坂御用地
赤坂御用地は、東京都港区赤坂に位置する日本の皇室関連施設が集まる広大な御用地で、皇族方の御所や宮邸が置かれているエリアである。
-
C.
赤坂見附駅
赤坂見附駅は、東京都港区に位置し、東京メトロ銀座線・丸ノ内線が交差する都心の主要地下鉄駅です。
-
D.
大手町
大手町 is a major business district in central Tokyo known for its concentration of corporate headquarters, financial institutions, and proximity to the Imperial Palace.
-
E.
高田馬場
高田馬場 is a bustling neighborhood in Tokyo’s Shinjuku ward known for its major train station, student population, and numerous eateries and entertainment spots.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd467f3b3081908261261301674c4e |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:10 a.m.