Triple
T5891653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness-shire |
E131003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former county of Scotland |
C5867
|
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 county of Scotland Context triple: [Inverness-shire, instanceOf, former county of Scotland]
-
A.
historic county of Scotland
chosen
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.
-
B.
region of Scotland
A region of Scotland is a geographically defined area within the country characterized by shared administrative boundaries, cultural identity, and physical landscape features.
-
C.
former county of Norway
A former county of Norway is an administrative region that previously functioned as a primary subnational division of the country but has since been merged, reorganized, or dissolved through governmental reform.
-
D.
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.
-
E.
registration county of Scotland
The registration county of Scotland is an administrative geographic unit historically used for organizing civil registration of births, marriages, and deaths, as well as certain statistical and legal purposes.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.