Triple

T30167328
Position Surface form Disambiguated ID Type / Status
Subject Regio VIII Aemilia E766830 entity
Predicate instanceOf P0 FINISHED
Object Augustan region of Italy C9370 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: Augustan region of Italy
Context triple: [Regio VIII Aemilia, instanceOf, Augustan region of Italy]
  • A. 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.
  • B. regio of Rome under Augustus
    A regio of Rome under Augustus was one of the fourteen administrative districts into which the emperor reorganized the city for more efficient governance, public order, and urban management.
  • C. 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.
  • D. historical region of Italy chosen
    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.
  • E. plain of Italy
    The plain of Italy is a broad, low-lying expanse of fertile land, most notably exemplified by the Po Valley, that stretches across northern Italy and supports intensive agriculture and dense human settlement.
  • 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_69f2247a968881909d79c18f2bfcb275 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:23 p.m.