Triple
T32657842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segedunum Roman Baths |
E834911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed Roman bathhouse |
C26298
|
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 Roman bathhouse Context triple: [Segedunum Roman Baths, instanceOf, reconstructed Roman bathhouse]
-
A.
ancient Roman bath
An ancient Roman bath is a public complex of interconnected rooms and pools designed for bathing, socializing, exercise, and relaxation, typically featuring heated and cold baths, steam rooms, and elaborate architectural decoration.
-
B.
historic bathing pavilion
A historic bathing pavilion is a traditionally designed waterfront structure that once served as a public facility for swimming, changing, and social recreation, often reflecting the architectural and cultural values of its era.
-
C.
ancient Roman gymnasium
An ancient Roman gymnasium was a public complex where citizens engaged in physical exercise, athletic training, and social interaction, often integrated with bathing facilities and educational activities.
-
D.
historic bath
chosen
A historic bath is a preserved or documented bathing facility of significant age that reflects the architectural, cultural, and social practices of its period.
-
E.
ancient Roman domus
An ancient Roman domus was a private urban residence for the wealthy, organized around interior courtyards and designed to provide both domestic comfort and social display while shielding family life from the street.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:08 a.m.