Triple
T12400940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashiyama-ku, Kyoto |
E296250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special ward of Kyoto City |
C31409
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: special ward of Kyoto City Context triple: [Higashiyama-ku, Kyoto, instanceOf, special ward of Kyoto City]
-
A.
district of Kyoto
A district of Kyoto is an administrative or historically defined area within the city of Kyoto, characterized by its own local governance functions, cultural identity, and community infrastructure.
-
B.
special ward of Osaka City
A special ward of Osaka City is a proposed administrative subdivision that would function with a high degree of local autonomy under Osaka’s metropolitan-style governance, similar to Tokyo’s special wards.
-
C.
special ward of Tokyo
A special ward of Tokyo is an autonomous local government unit within Tokyo Metropolis that functions similarly to a city, providing municipal services while operating under a unique administrative relationship with the metropolitan government.
-
D.
neighborhood of Kyoto
A neighborhood of Kyoto is a distinct local area within the city characterized by its blend of traditional machiya townhouses, temples or shrines, narrow streets, and community-focused shops and residences that reflect Kyoto’s historical and cultural identity.
-
E.
district of Osaka
A district of Osaka is an administrative subdivision within the city or prefecture of Osaka, characterized by its own local governance, neighborhoods, and community services.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.