Triple
T3165765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servicio de Administración Tributaria |
E66207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organismo público descentralizado |
C3952
|
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: organismo público descentralizado Context triple: [Servicio de Administración Tributaria, instanceOf, organismo público descentralizado]
-
A.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
B.
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.
-
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.
governmental organization
chosen
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
E.
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.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.