Triple
T33363336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irwin Union Bank, Columbus, Indiana (later work and expansions) |
E854282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bank building expansion |
C240
|
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: bank building expansion Context triple: [Irwin Union Bank, Columbus, Indiana (later work and expansions), instanceOf, bank building expansion]
-
A.
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.
-
B.
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.
-
C.
central bank building
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.
-
D.
museum building extension
A museum building extension is an added architectural volume or wing that expands a museum’s spatial capacity, functionality, and visitor experience while integrating with or reinterpreting the existing structure.
-
E.
building
chosen
A building is a constructed, often multi-level structure designed to provide shelter, space, and functional environments for human activities such as living, working, or storing goods.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.