Triple

T31413169
Position Surface form Disambiguated ID Type / Status
Subject Office of the Ombudsman (FDIC) E801322 entity
Predicate instanceOf P0 FINISHED
Object FDIC office C58833 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: FDIC office
Context triple: [Office of the Ombudsman (FDIC), instanceOf, FDIC office]
  • A. FDIC division chosen
    An FDIC division is an organizational unit within the Federal Deposit Insurance Corporation responsible for specific regulatory, supervisory, insurance, or administrative functions that support the agency’s mission to maintain stability and public confidence in the U.S. financial system.
  • B. branch of a Federal Reserve Bank
    A branch of a Federal Reserve Bank is a regional office that supports the operations, services, and policy functions of its parent Reserve Bank within a specific geographic area.
  • C. Federal Reserve Bank
    A Federal Reserve Bank is a regional institution within the U.S. central banking system that implements monetary policy, supervises and regulates member banks, provides financial services, and supports the stability of the national financial system.
  • D. Federal Reserve District
    A Federal Reserve District is a geographic region of the United States served by one of the twelve regional Federal Reserve Banks, responsible for implementing monetary policy, supervising member banks, and providing financial services within its boundaries.
  • E. financial institution location
    A financial institution location is a physical or virtual site where a financial organization conducts transactions, offers services, and interacts with customers or counterparties.
  • F. None of above.

Provenance (1 batch)

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_69f348c0dd648190bf2fd7642f78eb06 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 8:40 p.m.