Triple
T28176683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viborg County |
E715610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former county of Denmark |
C54499
|
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 Denmark Context triple: [Viborg County, instanceOf, former county of Denmark]
-
A.
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.
-
B.
Danish territory
Danish territory is the geographical area under the sovereignty of the Kingdom of Denmark, including continental Denmark, the Faroe Islands, and Greenland, where Danish law and governance apply.
-
C.
region of Denmark
A region of Denmark is a top-level administrative division responsible for coordinating healthcare, regional development, and certain public services across multiple municipalities within its geographic area.
-
D.
former Danish colony
A former Danish colony is a territory that was once under the political control and administration of Denmark but has since gained independence or been transferred to another sovereign state.
-
E.
Danish municipality
A Danish municipality is a local government administrative unit in Denmark responsible for providing public services, local planning, and governance within a defined geographic area.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:16 p.m.