Triple
T28006139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland state tax administration |
E707282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public 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: public revenue authority Context triple: [Maryland state tax administration, instanceOf, public revenue authority]
-
A.
revenue-collecting right
A revenue-collecting right is a legally recognized entitlement to receive specified income streams—such as taxes, fees, royalties, or tolls—generated by an asset, activity, or jurisdiction, without necessarily owning the underlying source.
-
B.
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.
-
C.
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.
-
D.
revenue block
A revenue block is a modular unit within a business model or financial system that represents a distinct, trackable source or stream of income.
-
E.
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.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8 p.m.