Triple
T294631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank Secrecy Act |
E6065
|
entity |
| Predicate | complianceRequires |
P5499
|
FINISHED |
| Object | internal controls at financial institutions |
—
|
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: internal controls at financial institutions | Statement: [Bank Secrecy Act, complianceRequires, internal controls at financial institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complianceRequires Context triple: [Bank Secrecy Act, complianceRequires, internal controls at financial institutions]
-
A.
hasConformanceRequirements
chosen
Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
-
B.
legalRequirement
Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
-
C.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
- 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.