Triple

T35847164
Position Surface form Disambiguated ID Type / Status
Subject Second Complex of Villa Arianna E1036244 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman residential complex 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 residential complex
Context triple: [Second Complex of Villa Arianna, instanceOf, ancient Roman residential complex]
  • 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. 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.
  • C. 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.
  • 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 agora
    An ancient Roman agora is a central public space in a Roman city used for markets, political gatherings, social interaction, and religious activities, typically surrounded by important civic and commercial buildings.
  • 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_69f76e1a29e8819088280f26096aeb55 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:06 p.m.