Triple
T31961900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humberside |
E816061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative county of England |
C44027
|
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 county of England Context triple: [Humberside, instanceOf, former administrative county of England]
-
A.
historic county of England
A historic county of England is a traditional geographic and cultural subdivision whose boundaries were established for administrative, judicial, and social purposes before modern local government reforms.
-
B.
former ceremonial county
chosen
A former ceremonial county is a geographic area in a country that once held official ceremonial or administrative status, such as having a lord-lieutenant or similar representative, but no longer functions in that capacity due to boundary changes or governmental reorganization.
-
C.
former metropolitan borough
A former metropolitan borough is a once-autonomous urban local government district that has been abolished or reorganized, typically through administrative restructuring or consolidation into a larger authority.
-
D.
sub-region of England
A sub-region of England is a defined geographic and administrative area within the country that groups together multiple counties or local authorities for planning, statistical, or governance purposes.
-
E.
former county of Denmark
A former county of Denmark is an obsolete administrative division that once functioned as a regional governing unit within the Kingdom of Denmark but has since been replaced or reorganized under newer territorial structures.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:09 a.m.