Triple

T31077852
Position Surface form Disambiguated ID Type / Status
Subject vicus Portae Salutaris interior E792017 entity
Predicate instanceOf P0 FINISHED
Object topographical feature of ancient Rome C25788 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: topographical feature of ancient Rome
Context triple: [vicus Portae Salutaris interior, instanceOf, topographical feature of ancient Rome]
  • A. topographical feature of ancient cities chosen
    A topographical feature of ancient cities is a natural or human-modified physical element of the urban landscape—such as hills, rivers, valleys, or terraces—that shaped the city’s layout, defenses, infrastructure, and social organization.
  • 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. area of ancient Rome
    An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
  • D. hill of Rome
    A hill of Rome is one of the elevated landforms within the city that historically shaped its topography, urban development, and cultural identity.
  • 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_69f224ccdbbc81909b0cdb4cc2d70c7a completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:02 p.m.