Triple
T21426004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference of Presidents of Spanish Autonomous Communities |
E528555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cooperative governance body |
C40022
|
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: cooperative governance body Context triple: [Conference of Presidents of Spanish Autonomous Communities, instanceOf, cooperative governance 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.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
C.
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.
-
D.
non-governmental public body
A non-governmental public body is an organization that, while independent of direct government control, performs functions or provides services of public interest, often operating under public law or with public funding and oversight.
-
E.
governance entity
chosen
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:48 p.m.