Triple
T16644809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl Brewery |
E404440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic brewery complex |
C8268
|
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: historic brewery complex Context triple: [Pearl Brewery, instanceOf, historic brewery complex]
-
A.
brewery complex
chosen
A brewery complex is a coordinated group of buildings and facilities where beer is produced, stored, packaged, and often served to the public, typically including brewing equipment, warehouses, administrative areas, and visitor spaces.
-
B.
historic industrial complex
A historic industrial complex is a large-scale, often multi-building site where past manufacturing, processing, or extractive activities took place, retaining significant architectural, technological, and cultural heritage value.
-
C.
historic industrial area
A historic industrial area is a district characterized by preserved or repurposed factories, warehouses, and infrastructure that reflect the industrial heritage and economic history of a place.
-
D.
historic blast furnace complex
A historic blast furnace complex is an industrial site, often preserved as heritage, where iron ore was once smelted at high temperatures in large furnaces along with associated structures such as casting houses, coke ovens, and worker facilities.
-
E.
historic mining complex
A historic mining complex is an integrated ensemble of former extraction, processing, and support facilities, structures, and landscapes that together illustrate the technological, economic, and social history of past mining activities.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:18 a.m.