Triple
T13785923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Analog Act |
E331256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal drug law |
C250
|
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: United States federal drug law Context triple: [Federal Analog Act, instanceOf, United States federal drug law]
-
A.
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.
-
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 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.
-
D.
United States federal law
chosen
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:11 p.m.