Triple
T11158706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Sales Tax (PST) |
E263978
|
entity |
| Predicate | mayBeCombinedAs |
P60771
|
FINISHED |
| Object | Harmonized Sales Tax (HST) |
—
|
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: Harmonized Sales Tax (HST) | Statement: [Provincial Sales Tax (PST), mayBeCombinedAs, Harmonized Sales Tax (HST)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeCombinedAs Context triple: [Provincial Sales Tax (PST), mayBeCombinedAs, Harmonized Sales Tax (HST)]
-
A.
mayBeFormedWhen
Indicates that one entity has the potential to come into existence or be created as a result of another entity, condition, or process.
-
B.
mayBeJointBetween
Indicates that two or more entities might potentially form or participate in a joint relationship, without asserting that the joint relationship definitely exists.
-
C.
canMerge
chosen
Indicates that two or more entities are compatible in such a way that they can be combined into a single unified entity or structure.
-
D.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e87fe9a881909540ecc4ed9b6b9f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.