Triple
T24032062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dry agents |
E595131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prohibition enforcement agents |
C38786
|
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: Prohibition enforcement agents Context triple: [Dry agents, instanceOf, Prohibition enforcement agents]
-
A.
Prohibition agent
chosen
A Prohibition agent is a law enforcement official responsible for investigating, preventing, and prosecuting the illegal production, distribution, and sale of alcohol during the Prohibition era.
-
B.
Prohibition-era case
A Prohibition-era case is a legal dispute or criminal proceeding arising during the U.S. Prohibition period (1920–1933), typically involving violations of alcohol bans, organized crime, or enforcement of related federal and state laws.
-
C.
Pinkerton detective
A Pinkerton detective is a private investigator employed by the Pinkerton National Detective Agency, historically known for security work, strikebreaking, and pursuing high-profile criminals in the United States.
-
D.
Kansas Bureau of Investigation agent
A Kansas Bureau of Investigation agent is a state-level law enforcement officer responsible for conducting criminal investigations, gathering and analyzing evidence, and supporting local agencies to uphold public safety and enforce Kansas laws.
-
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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:55 p.m.