Triple
T36311059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domestic Taxes Department |
E894068
|
entity |
| Predicate | usesTaxTypes |
P3166
|
FINISHED |
| Object | income tax |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: income tax | Statement: [Domestic Taxes Department, usesTaxTypes, income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTaxTypes Context triple: [Domestic Taxes Department, usesTaxTypes, income tax]
-
A.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
usesTariffSystem
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
C.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
D.
introducedTaxType
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
E.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
- F. None of above.
Provenance (3 batches)
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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:09 p.m.