Triple
T5622440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional council of Södermanland |
E147639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elected regional governing body |
C11221
|
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: elected regional governing body Context triple: [Regional council of Södermanland, instanceOf, elected regional governing body]
-
A.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
regional body of an international organization
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
-
C.
directly elected regional authority
chosen
A directly elected regional authority is a governing body at the subnational level whose members are chosen by popular vote to administer and make policy decisions for a specific geographic region.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:40 p.m.