Triple
T14016017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMEA |
E337205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-methamphetamine legislation |
C9682
|
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: anti-methamphetamine legislation Context triple: [CMEA, instanceOf, anti-methamphetamine legislation]
-
A.
anti-drug legislation
chosen
Anti-drug legislation comprises laws and regulations designed to control, restrict, or prohibit the production, distribution, possession, and use of certain drugs, often with the goals of protecting public health, reducing crime, and regulating pharmaceutical and recreational substances.
-
B.
drug control policy
Drug control policy is a framework of laws, regulations, and strategies designed to manage the production, distribution, and use of drugs to protect public health and safety.
-
C.
drug control treaty
A drug control treaty is an international legal agreement among states that establishes rules, obligations, and cooperative mechanisms for regulating, restricting, and monitoring the production, distribution, and use of controlled substances.
-
D.
drug control treaty regime
A drug control treaty regime is a system of international agreements, institutions, and norms designed to regulate the production, distribution, and consumption of controlled substances across states.
-
E.
drug control agency
A drug control agency is a governmental or intergovernmental body responsible for regulating, monitoring, and enforcing laws related to the production, distribution, prescription, and use of controlled substances to prevent abuse and ensure public safety.
- F. None of above.
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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.