Triple
T11974904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Nations drug control agreements |
E285014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | drug control treaty regime |
C30724
|
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: drug control treaty regime Context triple: [League of Nations drug control agreements, instanceOf, drug control treaty regime]
-
A.
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.
-
B.
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.
-
C.
illicit drug trade
The illicit drug trade is the illegal production, distribution, and sale of controlled substances through underground networks that evade regulation and law enforcement.
-
D.
drug policy evaluation mechanism
A drug policy evaluation mechanism is a systematic framework of methods, indicators, and processes used to assess the effectiveness, efficiency, and impacts of drug-related laws, regulations, and interventions.
-
E.
anti-drug legislation
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.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.