Triple
T33645055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa of Maxentius |
E861937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman villa complex |
C29737
|
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 villa complex Context triple: [Villa of Maxentius, instanceOf, ancient Roman villa complex]
-
A.
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.
-
B.
ancient guesthouse complex
An ancient guesthouse complex is a historical lodging facility composed of multiple interconnected structures and courtyards designed to accommodate travelers, provide communal services, and support trade or pilgrimage along important routes.
-
C.
imperial villa
chosen
An imperial villa is a luxurious countryside residence built and used by an emperor or ruling elite for retreat, governance, and display of power.
-
D.
Roman-Byzantine archaeological complex
A Roman-Byzantine archaeological complex is an integrated site containing architectural remains, artifacts, and stratified layers that document the transition and continuity between Roman and Byzantine periods in a specific region.
-
E.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.