Triple
T28775385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billingsgate Roman House and Baths |
E726518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman domestic building |
C29212
|
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 domestic building Context triple: [Billingsgate Roman House and Baths, instanceOf, Roman domestic building]
-
A.
ancient Roman domus
chosen
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.
-
B.
ancient Roman structure
An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
-
C.
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.
-
D.
Roman imperial residence
A Roman imperial residence is a grand, often fortified palace complex that served as the official home, administrative center, and ceremonial stage for the Roman emperor and his court.
-
E.
Roman cultural institution
A Roman cultural institution is an organized social, religious, political, or recreational structure—such as temples, forums, baths, theaters, or legal bodies—that shaped and reflected the values, practices, and public life of ancient Roman society.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:17 a.m.