Triple
T11744378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo 23 wards |
E279238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special wards of Tokyo |
C8260
|
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 wards of Tokyo Context triple: [Tokyo 23 wards, instanceOf, special wards of Tokyo]
-
A.
special ward of Tokyo
chosen
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.
-
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 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.
-
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
A special ward is a dedicated hospital unit that provides focused medical care and monitoring for patients with specific conditions, needs, or levels of acuity.
- F. None of above.
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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.