Triple
T7884598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamabad Excise and Taxation Department |
E183069
|
entity |
| Predicate | collectsTaxOn |
P25448
|
FINISHED |
| Object | motor vehicles |
—
|
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: motor vehicles | Statement: [Islamabad Excise and Taxation Department, collectsTaxOn, motor vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsTaxOn Context triple: [Islamabad Excise and Taxation Department, collectsTaxOn, motor vehicles]
-
A.
taxOn
chosen
Indicates that one entity imposes or applies a tax on another entity or item.
-
B.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
C.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
D.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
E.
isTaxExemptOn
Indicates that an entity is not required to pay taxes on a specified item, transaction, or income under applicable tax rules.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d4d09481909a61037243397eff |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:59 p.m.