Triple
T6119959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ombudsman of Ecuador |
E136457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous public authority |
C1300
|
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: autonomous public authority Context triple: [Ombudsman of Ecuador, instanceOf, autonomous public authority]
-
A.
independent administrative authority
chosen
An independent administrative authority is a public body, separate from the traditional executive hierarchy, endowed with regulatory or supervisory powers and functional autonomy to ensure impartial decision-making in a specific sector or policy area.
-
B.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
-
C.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
D.
administrative authority
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.
-
E.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:14 p.m.