Triple
T2412059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GST (Canada) |
E52216
|
entity |
| Predicate | leviedOn |
P25448
|
FINISHED |
| Object | value added at each stage of production and distribution |
—
|
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: value added at each stage of production and distribution | Statement: [GST (Canada), leviedOn, value added at each stage of production and distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leviedOn Context triple: [GST (Canada), leviedOn, value added at each stage of production and distribution]
-
A.
taxOn
chosen
Indicates that one entity imposes or applies a tax on another entity or item.
-
B.
positionOnTaxation
Indicates a stance or viewpoint an entity holds regarding tax policies, levels, or structures.
-
C.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
-
D.
positionOnTaxes
Indicates a stance or viewpoint an entity holds regarding tax policies or taxation issues.
-
E.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc928fd608190885fcde6746a06bc |
completed | March 7, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.