Triple
T22134241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahuslen |
E546984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swedish province |
C12995
|
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: Swedish province Context triple: [Bahuslen, instanceOf, Swedish province]
-
A.
province of Sweden
A province of Sweden is a historical and cultural region with traditional boundaries and identities that no longer serve as administrative units but remain important for heritage, regional identity, and statistical purposes.
-
B.
historical province of Sweden
chosen
A historical province of Sweden is a traditional geographic and cultural region with historical significance, distinct identity, and often unique customs, which no longer serves as an administrative unit but remains important in cultural and regional contexts.
-
C.
county of Sweden
A county of Sweden is an administrative region governed by a county administrative board and a regional council, responsible for implementing national policies and coordinating public services such as healthcare, transportation, and regional development.
-
D.
former province of Finland
A former province of Finland is an administrative region that existed under Finland’s historical provincial system but has since been reorganized or abolished in later territorial reforms.
-
E.
town in Sweden
A town in Sweden is an urban settlement recognized within the Swedish municipal system, typically featuring local governance, residential areas, services, and infrastructure that support the surrounding region.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.