Triple
T30332651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chishima Islands of Hokkaido Prefecture |
E771526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative jurisdiction |
C536
|
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 jurisdiction Context triple: [Chishima Islands of Hokkaido Prefecture, instanceOf, former administrative jurisdiction]
-
A.
former administrative territorial entity
chosen
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
former local municipality
A former local municipality is an administrative area that once had its own local government authority but has since been dissolved, merged, or restructured into a different governing entity.
-
C.
regional jurisdiction
A regional jurisdiction is a defined geographic area within a larger political or administrative system that has specific legal authority, governance responsibilities, and regulatory powers over matters within its boundaries.
-
D.
former subdivision of a country
A former subdivision of a country is an administrative region or territorial unit that once existed within a nation’s political structure but has since been reorganized, merged, renamed, or abolished.
-
E.
former rural district
A former rural district is an administrative subdivision that once governed a predominantly countryside area but has since been dissolved, merged, or restructured into a different territorial unit.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:53 p.m.