Triple
T12226968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maratha administration |
E291376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revenue system |
C5806
|
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 system Context triple: [Maratha administration, instanceOf, revenue system]
-
A.
revenue service
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.
system of taxation
chosen
A system of taxation is an organized framework of rules, rates, and procedures through which a governing authority collects financial contributions from individuals and entities to fund public expenditures and influence economic behavior.
-
C.
accounts receivable system
An accounts receivable system is a software solution that tracks customer invoices, manages incoming payments, and monitors outstanding balances to support accurate cash flow and financial reporting.
-
D.
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.
-
E.
technical commission system
A technical commission system is a structured framework of processes, tools, and governance used to plan, execute, verify, and document the commissioning and performance validation of technical systems or facilities.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.