Triple
T11158701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Sales Tax (PST) |
E263978
|
entity |
| Predicate | rateVariesBy |
P98150
|
FINISHED |
| Object | province |
—
|
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: province | Statement: [Provincial Sales Tax (PST), rateVariesBy, province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateVariesBy Context triple: [Provincial Sales Tax (PST), rateVariesBy, province]
-
A.
termVariesBy
Indicates that the value or meaning of a term changes depending on a specified factor, such as context, dimension, or condition.
-
B.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
C.
viewVariesAmong
Indicates that the way something is viewed, perceived, or interpreted differs across multiple entities or contexts.
-
D.
structureVariesBy
Indicates that the structure or configuration of one entity changes depending on or is different for another specified factor or context.
-
E.
titleVariesBy
Indicates that the title associated with an entity changes depending on context, conditions, or another varying attribute.
- 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_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. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.