Triple
T23307734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimiez Roman baths |
E590496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman baths |
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: Roman baths Context triple: [Cimiez Roman baths, instanceOf, Roman baths]
-
A.
ancient Roman bath
chosen
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 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.
-
D.
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.
-
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.
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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:05 p.m.