Triple
T7443062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Brewhouse (Olympia Brewing Company) |
E171802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic brewery building |
C8770
|
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 building Context triple: [Old Brewhouse (Olympia Brewing Company), instanceOf, historic brewery building]
-
A.
brewery complex
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 commercial building
A historic commercial building is a long-standing structure originally designed and used for business or trade that holds architectural, cultural, or historical significance.
-
C.
brewery
A brewery is a facility where beer is produced through the processes of mashing, fermenting, conditioning, and packaging, often combining industrial equipment with craft-based techniques.
-
D.
historic municipal building
A historic municipal building is a long-standing public structure, such as a city hall or courthouse, that has served governmental or civic functions and holds architectural, cultural, or historical significance for a community.
-
E.
historic industrial structure
chosen
A historic industrial structure is a preserved building or facility originally designed for manufacturing, processing, or other industrial activities, valued today for its architectural, technological, and cultural significance.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:13 p.m.