Triple

T10300412
Position Surface form Disambiguated ID Type / Status
Subject Via Latina E241612 entity
Predicate instanceOf P0 FINISHED
Object Roman infrastructure 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 infrastructure
Context triple: [Via Latina, instanceOf, Roman infrastructure]
  • A. 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.
  • B. Roman frontier
    The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
  • 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. Roman trade route
    A Roman trade route is a network of roads, sea lanes, and river passages used during the Roman Empire to transport goods, people, and information across its territories and beyond.
  • E. Roman settlement
    A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 11:44 a.m.