Triple
T16240340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumi-ku |
E394225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special ward-level subdivision of Sendai |
C37164
|
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 subdivision of Sendai Context triple: [Izumi-ku, instanceOf, special ward-level subdivision of Sendai]
-
A.
administrative ward of Sapporo
An administrative ward of Sapporo is a local government subdivision of the city that manages municipal services, governance, and community affairs within its designated urban area.
-
B.
special ward of Sapporo
A special ward of Sapporo is a proposed administrative subdivision within the city of Sapporo, modeled after Tokyo’s special wards, that would function as a local government unit with a degree of autonomy under Hokkaido Prefecture.
-
C.
subprefecture of Japan
A subprefecture of Japan is an administrative division below the prefectural level that manages local government functions for a specific region within a prefecture, often in geographically large or remote areas.
-
D.
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.
-
E.
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.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.