Triple
T26485700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquae Cutiliae |
E664813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman spa town |
C5442
|
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 spa town Context triple: [Aquae Cutiliae, instanceOf, ancient Roman spa town]
-
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.
Roman town
chosen
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
C.
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.
-
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.
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.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:30 a.m.