Triple
T7459012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Government of Tarapacá |
E176196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | decentralized public body |
C3811
|
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 public body Context triple: [Regional Government of Tarapacá, instanceOf, decentralized public 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.
ad hoc governmental body
An ad hoc governmental body is a temporary, specially formed public entity created by a government to address a specific issue, task, or crisis and dissolved once its purpose is fulfilled.
-
C.
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.
-
D.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
E.
non-departmental public body
chosen
A non-departmental public body is an organization that operates at arm’s length from government departments to carry out public functions, often with its own board and a degree of operational independence while remaining publicly accountable.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:36 p.m.