Triple
T3973256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Group on Evaluations and Compliance |
E92381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FATF working group |
C3188
|
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: FATF working group Context triple: [Working Group on Evaluations and Compliance, instanceOf, FATF working group]
-
A.
counter-terrorist financing initiative
A counter-terrorist financing initiative is a coordinated set of policies, processes, and tools designed to detect, prevent, and disrupt the flow of funds and financial support to terrorist organizations and activities.
-
B.
WCO body
A WCO body is a standardized, structured representation of data and metadata defined by the World Customs Organization to facilitate consistent, electronic exchange of customs-related information across international systems.
-
C.
intergovernmental working group framework
chosen
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
-
D.
IETF working group
An IETF working group is a collaborative, time-bounded team of experts chartered within the Internet Engineering Task Force to develop, discuss, and standardize specific Internet technologies or protocols.
-
E.
organ of the Egmont Group
An organ of the Egmont Group is a formal body or structural component within the Egmont Group responsible for coordinating, supporting, or overseeing specific functions related to international cooperation among Financial Intelligence Units.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:32 p.m.