Triple
T14284781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 港区 |
E354141
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | 東京23区 |
E279238
|
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: 東京23区 | Statement: [港区, locatedIn, 東京23区]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 東京23区 Context triple: [港区, locatedIn, 東京23区]
-
A.
東京都港区
東京都港区は、東京湾に面し大使館や企業本社、高級住宅地が集まる東京都心の行政区の一つです。
-
B.
Meguro Ward
Meguro Ward is a residential and commercial district in southwest Tokyo known for its urban neighborhoods, cultural sites, and convenient rail access to central Tokyo.
-
C.
Shibuya-ku
Shibuya-ku is a major commercial and entertainment ward in central Tokyo, Japan, known for its bustling shopping districts, nightlife, and the iconic Shibuya Crossing.
-
D.
Sumida ward
Sumida ward is a special ward in Tokyo, Japan, known for landmarks such as the Tokyo Skytree and its mix of traditional neighborhoods and modern urban development.
-
E.
Tokyo 23 wards
chosen
Tokyo 23 wards is the core urban area of Tokyo, Japan, consisting of 23 special municipalities that together form the densely populated and administratively distinct heart of the metropolis.
- 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_69fd647daf448190a7a9e4ab432977c4 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:10 a.m.