Triple
T10056982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendagi |
E208887
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Yanaka |
E373367
|
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: Yanaka | Statement: [Sendagi, adjacentTo, Yanaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yanaka Context triple: [Sendagi, adjacentTo, Yanaka]
-
A.
Yanaka
chosen
Yanaka is a traditional, temple-filled neighborhood in Tokyo known for its preserved old-town atmosphere, narrow lanes, and historic cemetery.
-
B.
Toyonaka
Toyonaka is a suburban city in Japan’s Kansai region known for its residential neighborhoods, educational institutions, and proximity to central Osaka.
-
C.
Komagome
Komagome is a residential and commercial neighborhood in Tokyo known for its traditional atmosphere, historic temples, and the renowned Rikugien Garden.
-
D.
Osawa
Osawa is a Japanese surname and place name that serves as an alternative spelling of "Ozawa."
-
E.
Bunkyō
Bunkyō is a central Tokyo ward known for its universities, historic temples, and quiet residential neighborhoods.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfae503881909b9f016da4e2207d |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a6567f14819086134cdf3a13aa9b |
completed | April 22, 2026, 10:43 a.m. |
Created at: March 30, 2026, 8:57 p.m.