Triple
T33326241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barley Hall |
E853270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed medieval townhouse |
C55946
|
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: reconstructed medieval townhouse Context triple: [Barley Hall, instanceOf, reconstructed medieval townhouse]
-
A.
reconstructed castle
A reconstructed castle is a historically inspired fortress or palace that has been rebuilt or extensively restored to approximate its original appearance and function, often using modern materials and techniques.
-
B.
medieval burgher houses
chosen
Medieval burgher houses are multi-story urban dwellings built by and for the middle-class townspeople of the Middle Ages, typically combining residential, commercial, and storage functions behind narrow street frontages.
-
C.
medieval mansion
A medieval mansion is a large, fortified residence of nobility featuring stone construction, great halls, defensive elements, and expansive grounds reflecting wealth and social status in the Middle Ages.
-
D.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
E.
medieval timber-framed building
A medieval timber-framed building is a structure whose load-bearing framework is made of exposed wooden beams, with the spaces between them filled by materials like wattle and daub, brick, or plaster, reflecting construction techniques common in Europe from the Middle Ages.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.