Triple

T2579283
Position Surface form Disambiguated ID Type / Status
Subject Reg D E57049 entity
Predicate complianceRequiredFor P40383 FINISHED
Object access to Federal Reserve services 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: access to Federal Reserve services | Statement: [Reg D, complianceRequiredFor, access to Federal Reserve services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: complianceRequiredFor
Context triple: [Reg D, complianceRequiredFor, access to Federal Reserve services]
  • A. providesCompliance
    Indicates that one entity supplies or ensures adherence to required rules, standards, or regulations for another entity.
  • B. requiresComplianceTestingBy
    Indicates that one entity must undergo compliance testing conducted or overseen by another entity.
  • C. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • D. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • E. communicationRequirement
    Indicates that one entity is obligated or expected to communicate with another entity under specified conditions or for a particular purpose.
  • F. None of above. chosen

Provenance (4 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_69ab4a4dca6481908c301f8e317396e7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3a9fd3c8190a521931e40cd801c completed March 7, 2026, 7:28 a.m.
PD Predicate disambiguation batch_69abd0cfeae08190aed03866ba071c5c completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd209d934819093600889af9104c3 completed March 7, 2026, 7:21 a.m.
Created at: March 6, 2026, 9:49 p.m.