Triple
T15042062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Federal Reserve District |
E378624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional bank district |
C30563
|
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: regional bank district Context triple: [St. Louis Federal Reserve District, instanceOf, regional bank district]
-
A.
Federal Reserve District
chosen
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.
-
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.
regional development bank
A regional development bank is a multilateral financial institution that provides loans, grants, and technical assistance to support economic and social development within a specific geographic region.
-
D.
regional center
A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
-
E.
planned regional development bank
A planned regional development bank is a proposed financial institution designed to mobilize and allocate long-term capital within a specific geographic region to support sustainable economic growth, infrastructure, and social development projects.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.