Triple
T21702617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodney District |
E535695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former territorial authority district |
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 territorial authority district Context triple: [Rodney District, instanceOf, former territorial authority district]
-
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 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.
-
C.
former non-metropolitan district
A former non-metropolitan district is an abolished local government district in England that once operated below county level outside major metropolitan areas, typically handling local services such as housing, planning, and waste collection.
-
D.
colonial district
A colonial district is an administrative subdivision established by a colonial power to govern, control, and organize a specific geographic area within its overseas territories.
-
E.
former urban district
A former urban district is an administrative subdivision of a city or town that previously existed as a distinct governing or statistical unit but has since been dissolved, merged, or reorganized.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:45 p.m.