Triple
T12210885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harima Province |
E290953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative division of Japan |
C7636
|
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 administrative division of Japan Context triple: [Harima Province, instanceOf, former administrative division of Japan]
-
A.
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.
-
B.
historical province of Japan
chosen
A historical province of Japan is a former administrative and geographic division that existed before the modern prefecture system, often retaining cultural and historical significance in regional identity.
-
C.
administrative division of Japan
An administrative division of Japan is a geographically defined area, such as a prefecture, municipality, or special ward, established by the government to organize local governance, public administration, and the delivery of services.
-
D.
former municipality of Japan
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.
-
E.
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.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.