Triple
T32433211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Finland Regional State Administrative Agency |
E828783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regional State Administrative Agency |
C15312
|
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: Regional State Administrative Agency Context triple: [Southern Finland Regional State Administrative Agency, instanceOf, Regional State Administrative Agency]
-
A.
territorial government agency
chosen
A territorial government agency is a public organization established by a territorial authority to administer laws, deliver services, and manage resources within a defined geographic area.
-
B.
state government agency
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
C.
state administrative board
A state administrative board is a government-appointed body that oversees, regulates, and implements specific public policies or administrative functions within a state’s jurisdiction.
-
D.
provincial government agency
A provincial government agency is a public-sector organization established by a provincial authority to implement policies, deliver services, and regulate activities within its jurisdiction.
-
E.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:55 a.m.