Triple
T6986005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleport Pottery |
E161962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic pottery factory |
C10647
|
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 pottery factory Context triple: [Middleport Pottery, instanceOf, historic pottery factory]
-
A.
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.
-
B.
historic industrial complex
chosen
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 company
A historic company is an established business organization that has operated over a significant period of time and is notable for its enduring impact, legacy, or role in historical events or developments.
-
D.
historic industrial structure
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.
-
E.
historic communal farm
A historic communal farm is a shared agricultural property where a community of people collectively lived and worked the land, reflecting past social, economic, and cultural practices of cooperative rural life.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:32 p.m.