Triple

T28660945
Position Surface form Disambiguated ID Type / Status
Subject Regio II Apulia et Calabria E725465 entity
Predicate instanceOf P0 FINISHED
Object Roman regio C54400 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 regio
Context triple: [Regio II Apulia et Calabria, instanceOf, Roman regio]
  • A. 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.
  • 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. area of ancient Rome
    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.
  • 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. rione of Rome
    A rione of Rome is a traditional administrative district within the historic center of the city, each with its own distinct history, identity, and urban character.
  • 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_69f01d84f5f0819087ab5e6143b14ed7 completed April 28, 2026, 2:37 a.m.
Created at: April 28, 2026, 4:58 a.m.