Triple

T347305
Position Surface form Disambiguated ID Type / Status
Subject Foreign Bank and Financial Accounts Reports E6968 entity
Predicate willfulViolationPenaltyType P3012 FINISHED
Object enhanced civil monetary penalty 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: enhanced civil monetary penalty | Statement: [Foreign Bank and Financial Accounts Reports, willfulViolationPenaltyType, enhanced civil monetary penalty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: willfulViolationPenaltyType
Context triple: [Foreign Bank and Financial Accounts Reports, willfulViolationPenaltyType, enhanced civil monetary penalty]
  • A. penaltyProvision
    Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
  • B. punishedBy
    Indicates that an entity receives punishment administered by another entity.
  • C. hasPunishment chosen
    Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
  • D. typeOfIncentive
    Indicates the specific kind or category of incentive associated with an entity or action.
  • E. exemptionType
    Indicates the specific category or kind of exemption that applies in a given context.
  • 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_69a2e7951ba08190960e90823b5078f3 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eb1a37c08190b1380f6bf8513a37 completed Feb. 28, 2026, 1:18 p.m.
PD Predicate disambiguation batch_69a2e95451a4819090f4e4fb9b21a493 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.