Triple
T28636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial Crimes Enforcement Network |
E570
|
entity |
| Predicate | mandate |
P68
|
FINISHED |
| Object | combat money laundering |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: combat money laundering | Statement: [Financial Crimes Enforcement Network, mandate, combat money laundering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandate Context triple: [Financial Crimes Enforcement Network, mandate, combat money laundering]
-
A.
mission
chosen
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
B.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
C.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
D.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- F. None of above.
Provenance (3 batches)
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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24925607c8190a9ce7ec834f3e5bb |
completed | Feb. 28, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69a2486bd74c81908d32be3c7d22f51f |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.