Triple
T37026829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimbin Hemp Embassy |
E916377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cannabis law reform organisation |
C65278
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cannabis law reform organisation Context triple: [Nimbin Hemp Embassy, instanceOf, cannabis law reform organisation]
-
A.
cannabis law reform event
A cannabis law reform event is a planned gathering or campaign activity focused on advocating for changes to cannabis-related legislation, policies, or public attitudes.
-
B.
drug user organization
A drug user organization is a collective, often led by people who use drugs, that advocates for their rights, health, and social inclusion while providing peer-based support and harm reduction services.
-
C.
criminal justice reform organization
A criminal justice reform organization is a group dedicated to changing laws, policies, and practices within the legal and correctional systems to promote fairness, reduce harm, and improve outcomes for impacted individuals and communities.
-
D.
drug policy experiment
A drug policy experiment is a structured, time-bound trial of alternative legal, regulatory, or public health approaches to drug control, designed to evaluate their impacts on outcomes such as use, harm, crime, and social equity.
-
E.
legalization program
A legalization program is an organized governmental or institutional initiative that formally grants legal status, rights, or protections to previously unauthorized or informal activities, entities, or individuals under defined conditions.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.