Triple
T4669343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hantescire |
E102923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic county name |
C12371
|
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: historic county name Context triple: [Hantescire, instanceOf, historic county name]
-
A.
historic county of England
chosen
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.
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.
-
D.
historical place name
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
E.
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.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.