Triple
T16689614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azabu |
E405559
|
entity |
| Predicate | hasSubdistrict |
P747
|
FINISHED |
| Object | Moto-Azabu |
E1231356
|
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: Moto-Azabu | Statement: [Azabu, hasSubdistrict, Moto-Azabu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moto-Azabu Context triple: [Azabu, hasSubdistrict, Moto-Azabu]
-
A.
Komagome
Komagome is a residential and commercial neighborhood in Tokyo known for its traditional atmosphere, historic temples, and the renowned Rikugien Garden.
-
B.
Funabashi
Funabashi is a major city in Chiba Prefecture, Japan, known as a residential and commercial hub within the Greater Tokyo metropolitan area.
-
C.
Minami-Azabu
Minami-Azabu is a residential and diplomatic district in Minato, Tokyo, known for its embassies, international schools, and upscale urban atmosphere.
-
D.
Nishi-Azabu
chosen
Nishi-Azabu is a fashionable, upscale neighborhood in Tokyo’s Minato ward, known for its trendy restaurants, nightlife, and proximity to areas like Roppongi and Hiroo.
-
E.
Omotesandō
Omotesandō is a fashionable, tree-lined avenue in Tokyo known for its high-end boutiques, modern architecture, and trendy cafés.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea80d88819091fc61ed3c01955a |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b27dcef481909ccfe4d3d604b1de |
completed | May 10, 2026, 4:29 p.m. |
Created at: April 10, 2026, 5:19 a.m.