Triple
T10797028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōnan Ward, Yokohama |
E254736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ward of Yokohama |
C17267
|
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: ward of Yokohama Context triple: [Kōnan Ward, Yokohama, instanceOf, ward of Yokohama]
-
A.
ward of Japan
chosen
A ward of Japan is an administrative subdivision of a major city, such as Tokyo’s special wards or the wards of designated cities, functioning as a local government unit with specific municipal responsibilities.
-
B.
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.
-
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.
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.
place in Tokyo
A place in Tokyo is a specific location within the Tokyo metropolitan area, such as a neighborhood, landmark, building, or public space, identifiable by its geographic position and cultural or functional significance.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.