Triple

T21865411
Position Surface form Disambiguated ID Type / Status
Subject Lupercal cave E539871 entity
Predicate instanceOf P0 FINISHED
Object Roman religious site C6858 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 religious site
Context triple: [Lupercal cave, instanceOf, Roman religious site]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. Roman town
    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.
  • E. ancient Roman structure chosen
    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.
  • 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_69e0c478f59081909d54302b57fc1ce3 completed April 16, 2026, 11:14 a.m.
Created at: April 16, 2026, 6:56 p.m.