Triple
T15512925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawara-ku |
E368759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special ward of Fukuoka City |
C35563
|
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 Fukuoka City Context triple: [Sawara-ku, instanceOf, special ward of Fukuoka City]
-
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 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.
-
C.
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.
-
D.
Ichinomiya
Ichinomiya is a conceptual class representing the highest-ranked Shinto shrine in a historical Japanese province, often serving as a central religious and cultural institution for the region.
-
E.
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.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 4:01 a.m.