Triple
T24288129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okazaki, Mikawa Province |
E605731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Japanese municipality |
C20813
|
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: former Japanese municipality Context triple: [Okazaki, Mikawa Province, instanceOf, former Japanese municipality]
-
A.
former municipality of Japan
chosen
A former municipality of Japan is an administrative unit such as a city, town, or village that once existed independently but has since been merged, dissolved, or reorganized under Japan’s local government system.
-
B.
former district of Japan
A former district of Japan is an administrative subdivision that once existed within a prefecture but has since been dissolved or merged due to municipal reorganization.
-
C.
prefectural-level city (historical)
A prefectural-level city (historical) is an administrative division that historically combined an urban center with its surrounding rural areas under a single prefecture-level government, often serving as a regional political, economic, and cultural hub.
-
D.
district of Japan
A district of Japan is an administrative unit within a prefecture that groups together multiple towns and villages, serving primarily as a geographic and statistical subdivision rather than a governing body.
-
E.
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.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:08 a.m.