Triple

T24572699
Position Surface form Disambiguated ID Type / Status
Subject Aurelian Walls segment near Porta Maggiore E608003 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman city wall segment C45439 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 city wall segment
Context triple: [Aurelian Walls segment near Porta Maggiore, instanceOf, ancient Roman city wall segment]
  • A. 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.
  • B. 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.
  • C. ancient Roman street
    An ancient Roman street is a paved public thoroughfare, typically constructed of stone blocks with raised sidewalks, drainage systems, and often lined with shops, houses, and public buildings, facilitating movement, trade, and social interaction within Roman cities.
  • D. city wall section chosen
    A city wall section is a discrete, contiguous portion of a defensive wall surrounding an urban area, typically defined by its structural features, length, and position between towers, gates, or corners.
  • E. medieval city wall
    A medieval city wall is a fortified defensive structure encircling a town or city, typically built of stone with towers, gates, and battlements to protect inhabitants from external threats.
  • 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_69e2c4cdab6c8190aae6e5d3de55c95e completed April 17, 2026, 11:39 p.m.
Created at: April 18, 2026, 2:28 a.m.