Triple

T15138354
Position Surface form Disambiguated ID Type / Status
Subject Lydney Park Roman temple E361615 entity
Predicate instanceOf P0 FINISHED
Object Roman temple complex C3145 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 temple complex
Context triple: [Lydney Park Roman temple, instanceOf, Roman temple complex]
  • A. ancient Roman temple chosen
    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. 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.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69d85a06450081909c5a14ea9851a15e completed April 10, 2026, 2:01 a.m.
Created at: April 10, 2026, 3:07 a.m.