Triple
T3882246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akershus |
E92851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical county |
C6321
|
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: historical county Context triple: [Akershus, instanceOf, historical county]
-
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.
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.
-
E.
traditional county
chosen
A traditional county is a historical administrative and geographic subdivision of a country, often predating modern local government structures and retaining cultural and identity significance despite changes in official boundaries.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:20 p.m.