Triple
T36849211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Excise Act, 2005 (for import-stage excise) |
E910630
|
entity |
| Predicate | taxEvent |
P186580
|
FINISHED |
| Object | import of goods into Pakistan |
—
|
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: import of goods into Pakistan | Statement: [Federal Excise Act, 2005 (for import-stage excise), taxEvent, import of goods into Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxEvent Context triple: [Federal Excise Act, 2005 (for import-stage excise), taxEvent, import of goods into Pakistan]
-
A.
taxCase
Indicates a legal case or proceeding whose primary subject is taxation or tax-related disputes between parties.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxCharacteristic
Indicates the specific tax-related property, status, or classification that applies to an entity or transaction.
-
D.
taxSchedule
Indicates the structured plan or timetable according to which taxes are calculated, applied, and/or collected.
-
E.
taxSupport
Indicates that one entity provides financial or tax-related assistance, backing, or resources to another entity.
- F. None of above. chosen
Provenance (4 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.