Triple

T36080272
Position Surface form Disambiguated ID Type / Status
Subject Roman Istria E1043625 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial territory C5440 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 territory
Context triple: [Roman Istria, instanceOf, Roman provincial territory]
  • A. Roman province chosen
    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.
  • B. Roman administrative district
    A Roman administrative district is a territorial unit governed by Roman officials for the purposes of taxation, legal jurisdiction, military organization, and local administration within the Roman state.
  • C. Roman regio
    A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
  • D. core territory of the Roman Empire
    The core territory of the Roman Empire comprises the Italian peninsula and the western-central Mediterranean heartlands that formed the political, economic, and cultural center of Roman power and administration.
  • E. 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.
  • 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_69f76e3154908190a6f702671c2bea08 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:08 p.m.