Triple
T18041592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misuse of Drugs Act 1971 |
E431664
|
entity |
| Predicate | penaltiesVaryBy |
P98150
|
FINISHED |
| Object | drug class |
—
|
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: drug class | Statement: [Misuse of Drugs Act 1971, penaltiesVaryBy, drug class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltiesVaryBy Context triple: [Misuse of Drugs Act 1971, penaltiesVaryBy, drug class]
-
A.
penaltyRules
Indicates the rules or conditions under which penalties are defined, applied, or enforced in a given context.
-
B.
penaltiesAdjustedBy
Indicates that one entity’s penalties are modified, recalculated, or otherwise changed as a result of another entity’s influence or action.
-
C.
penaltyProvision
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
D.
supportsPenalty
Indicates that one entity endorses, approves of, or is in favor of a particular penalty being applied to another entity or situation.
-
E.
rateVariesBy
chosen
Indicates that the rate of something changes depending on a specified factor, condition, or category.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfee78048190b3fada0eb3d28c77 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.