Triple
T30210663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peloponnese Region (administrative services) |
E768057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | decentralized administrative authority |
C14004
|
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: decentralized administrative authority Context triple: [Peloponnese Region (administrative services), instanceOf, decentralized administrative authority]
-
A.
autonomous administrative authority
An autonomous administrative authority is an independent public body, separate from direct government control, empowered to regulate, supervise, or decide specific administrative matters within a defined domain.
-
B.
administrative authority
chosen
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
C.
provincial authority
A provincial authority is a regional governing body responsible for administering laws, policies, and public services within a specific province under a broader national framework.
-
D.
central governmental authority
A central governmental authority is the primary governing body that holds ultimate decision-making power and administrative control over a state or political system.
-
E.
devolved government
A devolved government is a form of governance in which a central authority grants certain legislative and administrative powers to regional or local bodies, allowing them a degree of self-rule within a larger sovereign state.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:32 p.m.