Triple
T20899110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Exchange, Edinburgh |
E514621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former exchange building |
C34693
|
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: former exchange building Context triple: [Royal Exchange, Edinburgh, instanceOf, former exchange building]
-
A.
former stock exchange building
chosen
A former stock exchange building is a historic structure originally designed and used for securities trading and financial transactions, later repurposed for new civic, cultural, or commercial functions.
-
B.
former customs house
A former customs house is a building that once served as an official government facility for collecting duties and controlling the import and export of goods at a port, border, or trading center, but has since been repurposed or no longer fulfills that function.
-
C.
former post office building
A former post office building is a structure that once housed postal services but has since been repurposed or left vacant while retaining its historical and architectural characteristics.
-
D.
former town hall
A former town hall is a building that once served as the central administrative and civic meeting place for a municipality but has since been repurposed or no longer functions in that official capacity.
-
E.
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.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.