Triple
T36255295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Exchange (Brighton) |
E891916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former trading hall |
C6271
|
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 trading hall Context triple: [Corn Exchange (Brighton), instanceOf, former trading hall]
-
A.
former stock exchange building
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 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.
-
C.
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.
-
D.
former corn exchange
chosen
A former corn exchange is a historic building originally used as a marketplace for trading corn and other grains, later repurposed for new commercial, cultural, or civic functions.
-
E.
Renaissance trading hall
A Renaissance trading hall is a grand, often ornately decorated public building where merchants, financiers, and guilds gathered to conduct commerce, negotiate contracts, and exchange goods and information in a bustling urban marketplace.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.