Triple

T31077808
Position Surface form Disambiguated ID Type / Status
Subject vicus Portae Collinae E792015 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman neighborhood C11977 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 neighborhood
Context triple: [vicus Portae Collinae, instanceOf, ancient Roman neighborhood]
  • A. ancient Roman agora
    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 street chosen
    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.
  • C. ancient Roman domus
    An ancient Roman domus was a private urban residence for the wealthy, organized around interior courtyards and designed to provide both domestic comfort and social display while shielding family life from the street.
  • D. Roman town
    A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
  • E. Greco-Roman settlement
    A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
  • 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.