Triple
T11104121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surgeon’s House archaeological site |
E262583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman domus |
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: ancient Roman domus Context triple: [Surgeon’s House archaeological site, instanceOf, ancient Roman domus]
-
A.
Roman imperial household
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
B.
ancient Roman family
An ancient Roman family (familia) was a hierarchical household unit centered on the paterfamilias, encompassing blood relatives, adopted members, slaves, and clients bound together by legal authority, religious rites, and shared social status.
-
C.
ancient Greek house
An ancient Greek house is a domestic dwelling organized around a central open-air courtyard, featuring separate spaces for men and women, storage, and daily activities, typically constructed from mudbrick, stone, and timber.
-
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.
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.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.