Triple

T28847175
Position Surface form Disambiguated ID Type / Status
Subject macellum of Aezani E728484 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman marketplace building C31776 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 marketplace building
Context triple: [macellum of Aezani, instanceOf, ancient Roman marketplace building]
  • A. ancient Roman agora chosen
    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.
  • B. 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.
  • C. 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.
  • D. ancient Greek public building
    An ancient Greek public building is a communal structure, such as a temple, stoa, theater, or council house, designed to serve civic, religious, political, or social functions within the polis.
  • 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_69f0319e8e7c8190b37288c8845b9dbc completed April 28, 2026, 4:03 a.m.
Created at: April 28, 2026, 6:42 a.m.