Triple
T16703301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OECD Global Forum on Transparency and Exchange of Information for Tax Purposes |
E405901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tax transparency body |
C38263
|
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: tax transparency body Context triple: [OECD Global Forum on Transparency and Exchange of Information for Tax Purposes, instanceOf, tax transparency body]
-
A.
tax law organization
A tax law organization is an entity that provides specialized legal services, guidance, and advocacy related to tax regulations, compliance, and disputes for individuals, businesses, or governments.
-
B.
tax administration portal
A tax administration portal is a secure online platform that enables taxpayers, businesses, and tax authorities to file returns, make payments, access records, and manage all tax-related obligations and communications in one centralized system.
-
C.
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.
-
D.
tax research platform
A tax research platform is a digital system that aggregates, organizes, and analyzes tax laws, regulations, rulings, and guidance to help users efficiently find authoritative answers to complex tax questions.
-
E.
tax dispute resolution body
A tax dispute resolution body is an independent authority or tribunal that reviews and adjudicates disagreements between taxpayers and tax authorities over assessments, liabilities, or interpretations of tax law.
- F. None of above. chosen
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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.