Triple

T14179111
Position Surface form Disambiguated ID Type / Status
Subject Gallo-Roman E351407 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial culture C33548 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 provincial culture
Context triple: [Gallo-Roman, instanceOf, Roman provincial culture]
  • A. Roman provincial population
    The Roman provincial population comprised the diverse inhabitants of Rome’s conquered territories, including local elites, rural peasants, urban dwellers, merchants, and enslaved people, whose lives were shaped by varying degrees of Roman administration, culture, and legal status.
  • B. Roman cultural group
    A Roman cultural group is a community of people in ancient Rome and its territories who shared common language (Latin), social customs, religious practices, legal traditions, and artistic expressions that collectively defined Roman identity.
  • C. Roman cult
    A Roman cult is a religious group or practice in ancient Rome centered on the worship of a specific deity, emperor, or sacred concept, involving prescribed rituals, offerings, and communal observances.
  • D. Roman art
    Roman art is the visual and architectural expression of ancient Rome, characterized by its adaptation of Greek models, emphasis on realism and portraiture, grand public monuments, and propagandistic function in service of the state and emperors.
  • E. Roman province
    A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
  • F. None of above. chosen

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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 1:02 a.m.