Triple
T36638117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union Drugs Agency |
E904514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | drug policy agency |
C10842
|
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 policy agency Context triple: [European Union Drugs Agency, instanceOf, drug policy agency]
-
A.
drug control agency
chosen
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.
-
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 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.
-
D.
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.
-
E.
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.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.