Triple
T23207552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannabis Act |
E580500
|
entity |
| Predicate | setsPackagingRulesFor |
P8188
|
FINISHED |
| Object | cannabis products |
—
|
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: cannabis products | Statement: [Cannabis Act, setsPackagingRulesFor, cannabis products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsPackagingRulesFor Context triple: [Cannabis Act, setsPackagingRulesFor, cannabis products]
-
A.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
B.
settingOfRule
Indicates the contextual environment, domain, or circumstances within which a particular rule is defined and intended to apply.
-
C.
packagingStyle
Indicates the manner or format in which a product or item is packaged or presented.
-
D.
eligibilityRulesSetBy
Indicates that one party defines or establishes the criteria or rules determining another party’s eligibility for something.
-
E.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907d8be08190a100d99efaff9964 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.