Triple
T29989220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Trust Company branch buildings |
E761824
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | series of bank buildings |
C56620
|
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: series of bank buildings Context triple: [Cleveland Trust Company branch buildings, instanceOf, series of bank buildings]
-
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.
civic building complex
A civic building complex is a coordinated group of public structures and spaces designed to house governmental, administrative, and community services within a unified physical setting.
-
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.
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.
-
E.
red-brick building complex
A red-brick building complex is a clustered arrangement of interconnected or closely situated structures primarily constructed with red brick, often sharing architectural style, function, and shared spaces.
- F. None of above. chosen
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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:37 p.m.