Triple
T526623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Department of the Treasury national AML and CFT priorities |
E10932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory policy framework |
C1
|
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: regulatory policy framework Context triple: [U.S. Department of the Treasury national AML and CFT priorities, instanceOf, regulatory policy framework]
-
A.
policy report
chosen
A policy report is a structured document that analyzes a specific issue, evaluates options, and presents evidence-based recommendations to guide decision-making by policymakers or stakeholders.
-
B.
United States federal policy
United States federal policy is the body of laws, regulations, and official actions enacted or implemented by the federal government to address national issues and guide public and private behavior across the country.
-
C.
science policy document
A science policy document is a formal written record that outlines principles, guidelines, and strategic decisions governing the conduct, funding, regulation, and societal integration of scientific research and innovation.
-
D.
telecommunications policy concept
A telecommunications policy concept is a principle or framework that guides how governments and regulators manage, structure, and oversee communication networks and services to balance public interest, competition, innovation, and access.
-
E.
domestic policy program
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.