Triple
T36002682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakamura-ku, Nagoya |
E1041175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special ward-level division of Nagoya |
C64827
|
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-level division of Nagoya Context triple: [Nakamura-ku, Nagoya, instanceOf, special ward-level division of Nagoya]
-
A.
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.
-
B.
special ward of Fukuoka City
A special ward of Fukuoka City is a designated administrative subdivision within Fukuoka that possesses a degree of local governmental authority and specialized services distinct from other municipal districts.
-
C.
special ward-level subdivision of Sendai
A special ward-level subdivision of Sendai is an administrative unit within the city that functions similarly to a Tokyo-style special ward, possessing a degree of local self-governance while remaining under the broader jurisdiction of Sendai’s municipal government.
-
D.
administrative ward of Yokohama
An administrative ward of Yokohama is a local government subdivision of the city that manages municipal services, governance, and community affairs within its designated area.
-
E.
special ward of Kyoto City
A special ward of Kyoto City is a distinct administrative district within Kyoto that possesses a degree of local self-governance while remaining under the broader jurisdiction and services of the city government.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.