Triple
T294635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank Secrecy Act |
E6065
|
entity |
| Predicate | violationCanResultIn |
P3012
|
FINISHED |
| Object | civil penalties |
—
|
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: civil penalties | Statement: [Bank Secrecy Act, violationCanResultIn, civil penalties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violationCanResultIn Context triple: [Bank Secrecy Act, violationCanResultIn, civil penalties]
-
A.
violatedPrinciple
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
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.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.