Triple

T28660944
Position Surface form Disambiguated ID Type / Status
Subject Regio II Apulia et Calabria E725465 entity
Predicate instanceOf P0 FINISHED
Object administrative region of ancient Roman Italy C27184 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: administrative region of ancient Roman Italy
Context triple: [Regio II Apulia et Calabria, instanceOf, administrative region of ancient Roman Italy]
  • A. historical region of Italy
    A historical region of Italy is a geographically defined area that played a distinct political, cultural, or administrative role in Italy’s past, often predating or differing from the country’s modern regional boundaries.
  • B. former province of Italy
    A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
  • C. province of Italy
    A province of Italy is an administrative territorial division within an Italian region that groups together multiple municipalities under a shared local government and jurisdiction.
  • D. core territory of the Roman Empire chosen
    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 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.

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_69f01d84f5f0819087ab5e6143b14ed7 completed April 28, 2026, 2:37 a.m.
Created at: April 28, 2026, 4:58 a.m.