Triple
T17571681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckinghamshire and Hertfordshire |
E427954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pair of historic counties |
C39370
|
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: pair of historic counties Context triple: [Buckinghamshire and Hertfordshire, instanceOf, pair of historic counties]
-
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.
historic county of Scotland
A historic county of Scotland is a traditional territorial division that once served as an administrative and cultural unit, often retaining significance for identity, geography, and historical reference despite no longer having formal governmental functions.
-
C.
medieval county
A medieval county is a territorial and administrative unit governed by a count or similar noble, encompassing lands, settlements, and jurisdictions within a feudal hierarchy.
-
D.
shire county
A shire county is a traditional administrative division in England, typically encompassing both rural and urban areas, governed by a county council responsible for local services such as education, transport, and social care.
-
E.
former county town
A former county town is a settlement that once served as the administrative center of a county but no longer holds that official status.
- F. None of above. chosen
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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.