Triple
T30723472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consejerías de Extremadura |
E782212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional government ministry |
C3428
|
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 government ministry Context triple: [Consejerías de Extremadura, instanceOf, regional government ministry]
-
A.
regional government service
A regional government service is an administrative entity that delivers public programs, resources, and regulatory functions within a specific geographic area under the authority of a higher-level government.
-
B.
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.
-
C.
government ministry
chosen
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
-
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.
departmental government
A departmental government is a form of executive organization in which authority is divided among specialized departments, each headed by a minister or secretary responsible for a specific policy area.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:36 p.m.