Triple

T32484834
Position Surface form Disambiguated ID Type / Status
Subject Money Laundering Control Act of 1986 E830208 entity
Predicate establishesOffense P26615 FINISHED
Object 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: money laundering | Statement: [Money Laundering Control Act of 1986, establishesOffense, money laundering]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: establishesOffense
Context triple: [Money Laundering Control Act of 1986, establishesOffense, money laundering]
  • A. definesOffence chosen
    Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
  • B. offenceCognizable
    Indicates that the offence is of a type for which police may initiate investigation and arrest without requiring prior permission or a warrant from a magistrate.
  • C. typeOfOffenseAddressed
    Indicates the specific category or kind of offense that a given action, measure, or legal provision is intended to address.
  • D. offenseAgainst
    Indicates that one party has committed a harmful, illegal, or rule-violating act directed against another party or entity.
  • E. offenseDescription
    Indicates the specific nature or characterization of an offense, typically summarizing what violation or wrongdoing occurred.
  • 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_69f34920aa4081908d8fb0277414b911 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: May 1, 2026, 12:58 a.m.