Triple

T31077626
Position Surface form Disambiguated ID Type / Status
Subject Vicus Longus E792008 entity
Predicate instanceOf P0 FINISHED
Object neighborhood of ancient Rome C12791 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: neighborhood of ancient Rome
Context triple: [Vicus Longus, instanceOf, neighborhood of ancient Rome]
  • A. area of ancient Rome chosen
    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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. ancient Roman
    An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
  • 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.