Triple
T36419644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve Bank of Kansas City Headquarters |
E897114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central bank headquarters building |
C40310
|
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: central bank headquarters building Context triple: [Federal Reserve Bank of Kansas City Headquarters, instanceOf, central bank headquarters building]
-
A.
central bank building
chosen
A central bank building is a secure, often monumental facility that houses a nation's primary monetary authority, where currency issuance, financial regulation, and macroeconomic policy operations are conducted.
-
B.
bank building complex
A bank building complex is a group of interconnected structures and facilities designed to support a financial institution’s operations, including customer services, administrative offices, security areas, and supporting infrastructure.
-
C.
former bank headquarters
A former bank headquarters is a building that once served as the central administrative and operational office of a bank but has since been vacated, repurposed, or reassigned to a different primary use.
-
D.
series of bank buildings
A series of bank buildings is a conceptual class representing multiple related financial institution structures that share common architectural, functional, and branding characteristics across different locations or time periods.
-
E.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.