Triple
T14035395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Baths |
E337698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman bath |
C33982
|
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: ancient Roman bath Context triple: [Small Baths, instanceOf, ancient Roman bath]
-
A.
ancient Roman temple
An ancient Roman temple is a monumental religious structure, typically rectangular with a columned portico and elevated podium, dedicated to one or more deities and serving as a focal point for public worship and civic identity in Roman society.
-
B.
ancient Roman brothel
An ancient Roman brothel was a commercial establishment where sexual services were sold, often featuring small, sparsely furnished rooms, erotic wall paintings, and inscriptions that reflected the social, economic, and cultural dynamics of Roman urban life.
-
C.
ancient Roman agora
An ancient Roman agora is a central public space in a Roman city used for markets, political gatherings, social interaction, and religious activities, typically surrounded by important civic and commercial buildings.
-
D.
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.
-
E.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
- F. None of above. chosen
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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.