Triple
T21742253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SE121 Uppsala län |
E536686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statistical region of Sweden |
C45217
|
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: statistical region of Sweden Context triple: [SE121 Uppsala län, instanceOf, statistical region of Sweden]
-
A.
statistical region of the Czech Republic
A statistical region of the Czech Republic is a territorial unit defined primarily for the collection, analysis, and presentation of statistical data, often corresponding to NUTS or similar administrative divisions.
-
B.
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.
-
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.
Swedish-speaking area
A Swedish-speaking area is a geographic region where Swedish is predominantly used as the main language of everyday communication, education, and public life.
-
E.
district of Stockholm
A district of Stockholm is an administrative and geographical subdivision of Sweden’s capital city, characterized by its own local neighborhoods, services, and distinct urban identity within the greater metropolitan 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:49 p.m.