Triple
T8586642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uganda Revenue Authority |
E203321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revenue authority |
C23269
|
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: revenue authority Context triple: [Uganda Revenue Authority, instanceOf, revenue authority]
-
A.
revenue service
chosen
A revenue service is a governmental or organizational entity responsible for assessing, collecting, and enforcing taxes or other forms of income to fund public operations and services.
-
B.
autoridad fiscal
Una autoridad fiscal es la entidad gubernamental responsable de administrar, recaudar y fiscalizar los tributos, así como de hacer cumplir la normativa tributaria dentro de su jurisdicción.
-
C.
tax collector
A tax collector is an official responsible for assessing, collecting, and recording taxes owed by individuals and organizations in accordance with governing laws and regulations.
-
D.
taxpayer
A taxpayer is an individual or entity that is legally obligated to pay taxes to a governmental authority based on income, property, transactions, or other taxable activities.
-
E.
tax credit allocating authority
A tax credit allocating authority is an entity, typically a government agency or designated body, responsible for distributing, approving, and overseeing the allocation of tax credits to eligible projects, organizations, or individuals in accordance with statutory and regulatory criteria.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:22 p.m.