Triple
T23517056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harper government |
E574394
|
entity |
| Predicate | taxPolicyChange |
P152700
|
FINISHED |
| Object | reduced GST from 7% to 6% |
—
|
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: reduced GST from 7% to 6% | Statement: [Harper government, taxPolicyChange, reduced GST from 7% to 6%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxPolicyChange Context triple: [Harper government, taxPolicyChange, reduced GST from 7% to 6%]
-
A.
proposedTaxPolicyChange
Indicates that an entity has put forward a modification or new approach to existing tax rules or structures for consideration or implementation.
-
B.
typeOfTaxChange
Indicates a relationship where one entity represents a specific kind or category of tax modification described or classified by another entity.
-
C.
changesEstateTaxExemption
Indicates that an action or policy alters the threshold amount of an estate that is exempt from estate taxation.
-
D.
policyVariation
Indicates that one policy differs from another in certain terms, conditions, or parameters.
-
E.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa82a8448190bf7ad56137c5eb94 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:08 p.m.